Systems and methods for traffic optimization via system on chip of intermediary device

ABSTRACT

Embodiments described include systems and methods for delivering a network application. An intermediary device between a client device and a server hosting a network application establishes a connection with the network application. The intermediary device receives encoded application data and decodes the encoded application data. The application data is encoded graphics data or audio data. The decoded application data is renderable at the client device. The intermediary device transmits the decoded application graphics and/or audio data to a client application of the client application for rendering to provide user access to the network application.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority to andthe benefit of U.S. application Ser. No. 16/157,867, filed on Oct. 11,2018, and titled, “SYSTEMS AND METHODS FOR TRAFFIC OPTIMIZATION VIASYSTEM ON CHIP OF INTERMEDIARY DEVICE,” the entire contents of which areherein incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The present application generally relates to management of networkapplications, including but not limited to systems and methods for usingan intermediary device to optimize traffic from web, remotely-hosted,and software-as-a-service (SaaS) applications.

BACKGROUND

As the workforce of an enterprise becomes more mobile and work undervarious conditions, an individual can use one or more client devices,including personal devices, to access network resources such as webapplications. Due to differences between the client devices, userexperiences for network resources may be different when using differentclient devices.

BRIEF SUMMARY

The present disclosure is directed towards systems and methods fordelivering a network application. An intermediary device (sometimesreferred to herein as a NetScaler device or network appliance) mayinclude an HDX engine (also referred to herein as a remote sessionagent). The remote session agent may process remote session traffic atthe intermediary device using a System on Chip (or other processor orcomputing device of the intermediary device), for provisioning hostedapplications or desktops to a client device. In this regard, a receiverapplication (also referred to herein as a client application) canreceive and render the processed remote session traffic, and may nothave to further process or decode the processed remote session trafficprior to rendering at the client device. In a similar manner, contentprovided via a web, remotely-hosted or SaaS application may be processedor decoded at the intermediary device. For instance, the processedcontent may correspond to bitmap data, raw audio data, cascaded stylesheet (CSS) files (or similar files), etc. The processed content may betransmitted from the intermediary device to the client device forrendering (e.g., without further processing or decoding).

In one aspect, this disclosure is directed to a method for delivering anetwork application. The method can include establishing, by a deviceintermediary between a client device and a server hosting a networkapplication, a connection with the network application. The method caninclude receiving, by the device via the established connection,application data of the network application that includes at least oneof encoded graphics data or encoded audio data. The method can includedecoding, by the device, the received application data of the networkapplication, into at least one of decoded graphics data or decoded audiodata, for rendering at the client device. The method can includetransmitting, by the device, the at least one of decoded graphics dataor decoded audio data to a client application of the client device forrendering, to provide user access to the network application at theclient device.

In some embodiments, the method further includes causing an embeddedbrowser integrated in the client application to render the at least oneof decoded graphics data or decoded audio data. In some embodiments, theapplication data includes user interface display commands or messages.In some embodiments, the network application includes a remote-hostedapplication, a remote-hosted desktop, or a software-as-a-service (SaaS)application.

In some embodiments, decoding the received application data furtherincludes optimizing the received application data at a network level forrendering at the client device. In some embodiments, the method furtherincludes monitoring, by the device, the traffic communicated between thenetwork application and the client device. In some embodiments, themethod further includes providing, by the device, a secure browser forrendering the received application data at the device.

In some embodiments, the device is located closer to the client devicethan the server. In some embodiments, the method further includesmaintaining, by the device, a state of the network application when theclient device disconnects from a session of the network application viathe device. In some embodiments, the method further includesmaintaining, by the device, a state of the network application when asession of the network application via the device is transferred fromthe client device to another client device.

In another aspect, this disclosure is directed to a system fordelivering a network application. The system can include a deviceintermediary between a client device and a server hosting a networkapplication. The device can establish a connection with the networkapplication. The device can receive, via the established connection,application data of the network application that includes at least oneof encoded graphics data or encoded audio data. The device can decodethe received application data of the network application, into at leastone of decoded graphics data or decoded audio data, for rendering at theclient device. The device can transmit the at least one of decodedgraphics data or decoded audio data to a client application of theclient device for rendering, to provide user access to the networkapplication at the client device.

In some embodiments, the device is further configured to cause anembedded browser integrated in the client application to render the atleast one of decoded graphics data or decoded audio data. In someembodiments, the application data comprises user interface displaycommands or messages. In some embodiments, the network applicationincludes a remote-hosted application, a remote-hosted desktop, or asoftware-as-a-service (SaaS) application.

In some embodiments, the device is further configured to optimize thereceived application data at a network level for rendering at the clientdevice. In some embodiments, the device is further configured to monitorthe traffic communicated between the network application and the clientdevice. In some embodiments, the device is further configured to providea secure browser for rendering the received application data at thedevice.

In some embodiments, the device is located closer to the client devicethan the server. In some embodiments, the device is further configuredto maintain a state of the network application when the client devicedisconnects from a session of the network application via the device. Insome embodiments, the device is further configured to maintain a stateof the network application when a session of the network application viathe device is transferred from the client device to another clientdevice.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, aspects, features, and advantages ofthe present solution will become more apparent and better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram of embodiments of a computing device;

FIG. 2 is a block diagram of an illustrative embodiment of cloudservices for use in accessing resources;

FIG. 3 is a block diagram of an example embodiment of an enterprisemobility management system;

FIG. 4 is a block diagram of a system 400 of an embedded browser;

FIG. 5 is a block diagram of an example embodiment of a system for usinga secure browser;

FIG. 6 is an example representation of an implementation for browserredirection using a secure browser plug-in;

FIG. 7 is a block diagram of example embodiment of a system of using asecure browser;

FIG. 8 is a block diagram of an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s);

FIG. 9 is an example process flow for using local embedded browser(s)and hosted secured browser(s);

FIG. 10 is an example embodiment of a system for managing user access towebpages;

FIG. 11 is a block diagram of one embodiment of a system for deliveringa network application; and

FIG. 12 is a flow diagram of one embodiment of a method for delivering anetwork application.

The features and advantages of the present solution will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements.

DETAILED DESCRIPTION

For purposes of reading the description of the various embodimentsbelow, the following descriptions of the sections of the specificationand their respective contents may be helpful:

Section A describes a computing environment which may be useful forpracticing embodiments described herein.

Section B describes systems and methods for an embedded browser.

Section C describes systems and methods for delivering a networkapplication.

A. Computing Environment

Prior to discussing the specifics of embodiments of the systems andmethods detailed herein in Section B, it may be helpful to discuss thecomputing environments in which such embodiments may be deployed.

As shown in FIG. 1, computer 101 may include one or more processors 103,volatile memory 122 (e.g., random access memory (RAM)), non-volatilememory 128 (e.g., one or more hard disk drives (HDDs) or other magneticor optical storage media, one or more solid state drives (SSDs) such asa flash drive or other solid state storage media, one or more hybridmagnetic and solid state drives, and/or one or more virtual storagevolumes, such as a cloud storage, or a combination of such physicalstorage volumes and virtual storage volumes or arrays thereof), userinterface (UI) 123, one or more communications interfaces 118, andcommunication bus 150. User interface 123 may include graphical userinterface (GUI) 124 (e.g., a touchscreen, a display, etc.) and one ormore input/output (I/O) devices 126 (e.g., a mouse, a keyboard, amicrophone, one or more speakers, one or more cameras, one or morebiometric scanners, one or more environmental sensors, one or moreaccelerometers, etc.). Non-volatile memory 128 stores operating system115, one or more applications 116, and data 117 such that, for example,computer instructions of operating system 115 and/or applications 116are executed by processor(s) 103 out of volatile memory 122. In someembodiments, volatile memory 122 may include one or more types of RAMand/or a cache memory that may offer a faster response time than a mainmemory. Data may be entered using an input device of GUI 124 or receivedfrom I/O device(s) 126. Various elements of computer 101 may communicatevia one or more communication buses, shown as communication bus 150.

Computer 101 as shown in FIG. 1 is shown merely as an example, asclients, servers, intermediary and other networking devices and may beimplemented by any computing or processing environment and with any typeof machine or set of machines that may have suitable hardware and/orsoftware capable of operating as described herein. Processor(s) 103 maybe implemented by one or more programmable processors to execute one ormore executable instructions, such as a computer program, to perform thefunctions of the system. As used herein, the term “processor” describescircuitry that performs a function, an operation, or a sequence ofoperations. The function, operation, or sequence of operations may behard coded into the circuitry or soft coded by way of instructions heldin a memory device and executed by the circuitry. A “processor” mayperform the function, operation, or sequence of operations using digitalvalues and/or using analog signals. In some embodiments, the “processor”can be embodied in one or more application specific integrated circuits(ASICs), microprocessors, digital signal processors (DSPs), graphicsprocessing units (GPUs), microcontrollers, field programmable gatearrays (FPGAs), programmable logic arrays (PLAs), multi-core processors,or general-purpose computers with associated memory. The “processor” maybe analog, digital or mixed-signal. In some embodiments, the “processor”may be one or more physical processors or one or more “virtual” (e.g.,remotely located or “cloud”) processors. A processor including multipleprocessor cores and/or multiple processors multiple processors mayprovide functionality for parallel, simultaneous execution ofinstructions or for parallel, simultaneous execution of one instructionon more than one piece of data.

Communications interfaces 118 may include one or more interfaces toenable computer 101 to access a computer network such as a Local AreaNetwork (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN),or the Internet through a variety of wired and/or wireless or cellularconnections.

In described embodiments, the computing device 101 may execute anapplication on behalf of a user of a client computing device. Forexample, the computing device 101 may execute a virtual machine, whichprovides an execution session within which applications execute onbehalf of a user or a client computing device, such as a hosted desktopsession. The computing device 101 may also execute a terminal servicessession to provide a hosted desktop environment. The computing device101 may provide access to a computing environment including one or moreof: one or more applications, one or more desktop applications, and oneor more desktop sessions in which one or more applications may execute.

Additional details of the implementation and operation of networkenvironment, computer 101 and client and server computers may be asdescribed in U.S. Pat. No. 9,538,345, issued Jan. 3, 2017 to CitrixSystems, Inc. of Fort Lauderdale, Fla., the teachings of which arehereby incorporated herein by reference.

B. Systems and Methods for an Embedded Browser

The present disclosure is directed towards systems and methods of anembedded browser. A client application executing on a client device canallow a user to access applications (apps) that are served from and/orhosted on one or more servers, such as web applications andsoftware-as-a-service (SaaS) applications (hereafter sometimes generallyreferred to as network applications). A browser that is embedded orintegrated with the client application can render to the user a networkapplication that is accessed or requested via the client application,and can enable interactivity between the user and the networkapplication. The browser is sometimes referred to as an embeddedbrowser, and the client application with embedded browser (CEB) issometimes referred to as a workspace application. The client applicationcan establish a secure connection to the one or more servers to providean application session for the user to access the network applicationusing the client device and the embedded browser. The embedded browsercan be integrated with the client application to ensure that trafficrelated to the network application is routed through and/or processed inthe client application, which can provide the client application withreal-time visibility to the traffic (e.g., when decrypted through theclient application), and user interactions and behavior. The embeddedbrowser can provide a seamless experience to a user as the networkapplication is requested via the user interface (shared by the clientapplication and the embedded browser) and rendered through the embeddedbrowser within the same user interface.

The client application can terminate one end of a secured connectionestablished with a server of a network application, such as a securesockets layer (SSL) virtual private network (VPN) connection. The clientapplication can receive encrypted traffic from the network application,and can decrypt the traffic before further processing (e.g., renderingby the embedded browser). The client application can monitor thereceived traffic (e.g., in encrypted packet form), and also have fullvisibility into the decrypted data stream and/or the SSL stack. Thisvisibility can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control (e.g., to improve performance,service level), and collection and production of analytics. Forinstance, the local CEB can provide an information technology (IT)administrator with a controlled system for deploying web and SaaSapplications through the CEB, and allow the IT administrator to setpolicies or configurations via the CEB for performing any of theforgoing activities.

Many web and SaaS delivered applications connect from web servers togeneric browsers (e.g., Internet Explorer, Firefox, and so on) of users.Once authenticated, the entire session of such a network application isencrypted. However, in this scenario, an administrator may not havevisibility, analytics, or control of the content entering the networkapplication from the user's digital workspace, or the content leavingthe network application and entering the user's digital workspace.Moreover, content of a network application viewed in a generic browsercan be copied or downloaded (e.g., by a user or program) to potentiallyany arbitrary application or device, resulting in a possible breach indata security.

This present systems and methods can ensure that traffic associated witha network application is channeled through a CEB. By way ofillustration, when a user accesses a SaaS web service with securityassertion markup language (SAML) enabled for instance, the correspondingaccess request can be forwarded to a designated gateway service thatdetermines, checks or verifies if the CEB was used to make the accessrequest. Responsive to determining that a CEB was used to make theaccess request, the gateway service can perform or provideauthentication and single-sign-on (SSO), and can allow the CEB toconnect directly to the SaaS web service. Encryption (e.g., standardencryption) can be used for the application session between the CEB andthe SaaS web service. When the content from the web service isunencrypted in the CEB to the viewed via the embedded browser, and/orwhen input is entered via the CEB, the CEB can provide added services onselective application-related information for control and analytics forinstance. For example, an analytics agent or application programminginterface (API) can be embedded in the CEB to provide or perform theadded services.

The CEB (sometimes referred to as workspace application or receiver) caninteroperate with one or more gateway services, intermediaries and/ornetwork servers (sometimes collectively referred to as cloud services orCitrix Cloud) to provide access to a network application. Features andelements of an environment related to the operation of an embodiment ofcloud services are described below.

FIG. 2 illustrates an embodiment of cloud services for use in accessingresources including network applications. The cloud services can includean enterprise mobility technical architecture 200, which can include anaccess gateway 260 in one illustrative embodiment. The architecture canbe used in a bring-your-own-device (BYOD) environment for instance. Thearchitecture can enable a user of a client device 202 (e.g., a mobile orother device) to both access enterprise or personal resources from aclient device 202, and use the client device 202 for personal use. Theuser may access such enterprise resources 204 or enterprise services 208via a client application executing on the client device 202. The usermay access such enterprise resources 204 or enterprise services 208using a client device 202 that is purchased by the user or a clientdevice 202 that is provided by the enterprise to user. The user mayutilize the client device 202 for business use only or for business andpersonal use. The client device may run an iOS operating system, andAndroid operating system, or the like. The enterprise may choose toimplement policies to manage the client device 202. The policies may beimplanted through a firewall or gateway in such a way that the clientdevice may be identified, secured or security verified, and providedselective or full access to the enterprise resources. The policies maybe client device management policies, mobile application managementpolicies, mobile data management policies, or some combination of clientdevice, application, and data management policies. A client device 202that is managed through the application of client device managementpolicies may be referred to as an enrolled device. The client devicemanagement policies can be applied via the client application forinstance.

In some embodiments, the operating system of the client device may beseparated into a managed partition 210 and an unmanaged partition 212.The managed partition 210 may have policies applied to it to secure theapplications running on and data stored in the managed partition. Theapplications running on the managed partition may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the client device management system when that application isexecuting on the device. By operating in accordance with theirrespective policy file(s), each application may be allowed or restrictedfrom communications with one or more other applications and/orresources, thereby creating a virtual partition. Thus, as used herein, apartition may refer to a physically partitioned portion of memory(physical partition), a logically partitioned portion of memory (logicalpartition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapps as described herein (virtual partition). Stated differently, byenforcing policies on managed apps, those apps may be restricted to onlybe able to communicate with other managed apps and trusted enterpriseresources, thereby creating a virtual partition that is not accessibleby unmanaged apps and devices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The client applicationcan include a secure application launcher 218. The secure applicationsmay be secure native applications 214, secure remote applications 222executed by the secure application launcher 218, virtualizationapplications 226 executed by the secure application launcher 218, andthe like. The secure native applications 214 may be wrapped by a secureapplication wrapper 220. The secure application wrapper 220 may includeintegrated policies that are executed on the client device 202 when thesecure native application is executed on the device. The secureapplication wrapper 220 may include metadata that points the securenative application 214 running on the client device 202 to the resourceshosted at the enterprise that the secure native application 214 mayrequire to complete the task requested upon execution of the securenative application 214. The secure remote applications 222 executed by asecure application launcher 218 may be executed within the secureapplication launcher application 218. The virtualization applications226 executed by a secure application launcher 218 may utilize resourceson the client device 202, at the enterprise resources 204, and the like.The resources used on the client device 202 by the virtualizationapplications 226 executed by a secure application launcher 218 mayinclude user interaction resources, processing resources, and the like.The user interaction resources may be used to collect and transmitkeyboard input, mouse input, camera input, tactile input, audio input,visual input, gesture input, and the like. The processing resources maybe used to present a user interface, process data received from theenterprise resources 204, and the like. The resources used at theenterprise resources 204 by the virtualization applications 226 executedby a secure application launcher 218 may include user interfacegeneration resources, processing resources, and the like. The userinterface generation resources may be used to assemble a user interface,modify a user interface, refresh a user interface, and the like. Theprocessing resources may be used to create information, readinformation, update information, delete information, and the like. Forexample, the virtualization application may record user interactionsassociated with a graphical user interface (GUI) and communicate them toa server application where the server application may use the userinteraction data as an input to the application operating on the server.In this arrangement, an enterprise may elect to maintain the applicationon the server side as well as data, files, etc., associated with theapplication. While an enterprise may elect to “mobilize” someapplications in accordance with the principles herein by securing themfor deployment on the client device (e.g., via the client application),this arrangement may also be elected for certain applications. Forexample, while some applications may be secured for use on the clientdevice, others might not be prepared or appropriate for deployment onthe client device so the enterprise may elect to provide the mobile useraccess to the unprepared applications through virtualization techniques.As another example, the enterprise may have large complex applicationswith large and complex data sets (e.g., material resource planningapplications) where it would be very difficult, or otherwiseundesirable, to customize the application for the client device so theenterprise may elect to provide access to the application throughvirtualization techniques. As yet another example, the enterprise mayhave an application that maintains highly secured data (e.g., humanresources data, customer data, engineering data) that may be deemed bythe enterprise as too sensitive for even the secured mobile environmentso the enterprise may elect to use virtualization techniques to permitmobile access to such applications and data. An enterprise may elect toprovide both fully secured and fully functional applications on theclient device. The enterprise can use a client application, which caninclude a virtualization application, to allow access to applicationsthat are deemed more properly operated on the server side. In anembodiment, the virtualization application may store some data, files,etc., on the mobile phone in one of the secure storage locations. Anenterprise, for example, may elect to allow certain information to bestored on the phone while not permitting other information.

In connection with the virtualization application, as described herein,the client device may have a virtualization application that is designedto present GUIs and then record user interactions with the GUI. Thevirtualization application may communicate the user interactions to theserver side to be used by the server side application as userinteractions with the application. In response, the application on theserver side may transmit back to the client device a new GUI. Forexample, the new GUI may be a static page, a dynamic page, an animation,or the like, thereby providing access to remotely located resources.

The secure applications may access data stored in a secure datacontainer 228 in the managed partition 210 of the client device. Thedata secured in the secure data container may be accessed by the securewrapped applications 214, applications executed by a secure applicationlauncher 222, virtualization applications 226 executed by a secureapplication launcher 218, and the like. The data stored in the securedata container 228 may include files, databases, and the like. The datastored in the secure data container 228 may include data restricted to aspecific secure application 230, shared among secure applications 232,and the like. Data restricted to a secure application may include securegeneral data 234 and highly secure data 238. Secure general data may usea strong form of encryption such as Advanced Encryption Standard (AES)128-bit encryption or the like, while highly secure data 238 may use avery strong form of encryption such as AES 256-bit encryption. Datastored in the secure data container 228 may be deleted from the deviceupon receipt of a command from the device manager 224. The secureapplications may have a dual-mode option 240. The dual mode option 240may present the user with an option to operate the secured applicationin an unsecured or unmanaged mode. In an unsecured or unmanaged mode,the secure applications may access data stored in an unsecured datacontainer 242 on the unmanaged partition 212 of the client device 202.The data stored in an unsecured data container may be personal data 244.The data stored in an unsecured data container 242 may also be accessedby unsecured applications 248 that are running on the unmanagedpartition 212 of the client device 202. The data stored in an unsecureddata container 242 may remain on the client device 202 when the datastored in the secure data container 228 is deleted from the clientdevice 202. An enterprise may want to delete from the client deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The client device 202 may connect to enterprise resources 204 andenterprise services 208 at an enterprise, to the public Internet 248,and the like. The client device may connect to enterprise resources 204and enterprise services 208 through virtual private network connections.The virtual private network connections, also referred to as microVPN orapplication-specific VPN, may be specific to particular applications(e.g., as illustrated by microVPNs 250), particular devices, particularsecured areas on the client device (e.g., as illustrated by O/S VPN252), and the like. For example, each of the wrapped applications in thesecured area of the phone may access enterprise resources through anapplication specific VPN such that access to the VPN would be grantedbased on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 254. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 258. The authentication service 258 may thengrant to the user access to multiple enterprise resources 204, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 204.

The virtual private network connections may be established and managedby an access gateway 260. The access gateway 260 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 204 to the client device 202. The access gatewaymay also re-route traffic from the client device 202 to the publicInternet 248, enabling the client device 202 to access publiclyavailable and unsecured applications that run on the public Internet248. The client device may connect to the access gateway via a transportnetwork 262. The transport network 262 may use one or more transportprotocols and may be a wired network, wireless network, cloud network,local area network, metropolitan area network, wide area network, publicnetwork, private network, and the like.

The enterprise resources 204 may include email servers, file sharingservers, SaaS/Web applications, Web application servers, Windowsapplication servers, and the like. Email servers may include Exchangeservers, Lotus Notes servers, and the like. File sharing servers mayinclude ShareFile servers, and the like. SaaS applications may includeSalesforce, and the like. Windows application servers may include anyapplication server that is built to provide applications that areintended to run on a local Windows operating system, and the like. Theenterprise resources 204 may be premise-based resources, cloud basedresources, and the like. The enterprise resources 204 may be accessed bythe client device 202 directly or through the access gateway 260. Theenterprise resources 204 may be accessed by the client device 202 via atransport network 262. The transport network 262 may be a wired network,wireless network, cloud network, local area network, metropolitan areanetwork, wide area network, public network, private network, and thelike.

Cloud services can include an access gateway 260 and/or enterpriseservices 208. The enterprise services 208 may include authenticationservices 258, threat detection services 264, device manager services224, file sharing services 268, policy manager services 270, socialintegration services 272, application controller services 274, and thelike. Authentication services 258 may include user authenticationservices, device authentication services, application authenticationservices, data authentication services and the like. Authenticationservices 258 may use certificates. The certificates may be stored on theclient device 202, by the enterprise resources 204, and the like. Thecertificates stored on the client device 202 may be stored in anencrypted location on the client device, the certificate may betemporarily stored on the client device 202 for use at the time ofauthentication, and the like. Threat detection services 264 may includeintrusion detection services, unauthorized access attempt detectionservices, and the like. Unauthorized access attempt detection servicesmay include unauthorized attempts to access devices, applications, data,and the like. Device management services 224 may include configuration,provisioning, security, support, monitoring, reporting, anddecommissioning services. File sharing services 268 may include filemanagement services, file storage services, file collaboration services,and the like. Policy manager services 270 may include device policymanager services, application policy manager services, data policymanager services, and the like. Social integration services 272 mayinclude contact integration services, collaboration services,integration with social networks such as Facebook, Twitter, andLinkedIn, and the like. Application controller services 274 may includemanagement services, provisioning services, deployment services,assignment services, revocation services, wrapping services, and thelike.

The enterprise mobility technical architecture 200 may include anapplication store 278. The application store 278 may include unwrappedapplications 280, pre-wrapped applications 282, and the like.Applications may be populated in the application store 278 from theapplication controller 274. The application store 278 may be accessed bythe client device 202 through the access gateway 260, through the publicInternet 248, or the like. The application store may be provided with anintuitive and easy to use User Interface.

A software development kit 284 may provide a user the capability tosecure applications selected by the user by providing a secure wrapperaround the application. An application that has been wrapped using thesoftware development kit 284 may then be made available to the clientdevice 202 by populating it in the application store 278 using theapplication controller 274.

The enterprise mobility technical architecture 200 may include amanagement and analytics capability. The management and analyticscapability may provide information related to how resources are used,how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 3 depicts is an illustrative embodiment of an enterprise mobilitymanagement system 300. Some of the components of the mobility managementsystem 200 described above with reference to FIG. 2 have been omittedfor the sake of simplicity. The architecture of the system 300 depictedin FIG. 3 is similar in many respects to the architecture of the system200 described above with reference to FIG. 2 and may include additionalfeatures not mentioned above.

In this case, the left hand side represents an enrolled client device302 with a client agent 304, which interacts with gateway server 306 toaccess various enterprise resources 308 and services 309 such as Web orSaaS applications, Exchange, Sharepoint, public-key infrastructure (PKI)Resources, Kerberos Resources, Certificate Issuance service, as shown onthe right hand side above. The gateway server 306 can includeembodiments of features and functionalities of the cloud services, suchas access gateway 260 and application controller functionality. Althoughnot specifically shown, the client agent 304 may be part of, and/orinteract with the client application which can operate as an enterpriseapplication store (storefront) for the selection and/or downloading ofnetwork applications.

The client agent 304 can act as a UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX) or IndependentComputing Architecture (ICA) display remoting protocol. The client agent304 can also support the installation and management of nativeapplications on the client device 302, such as native iOS or Androidapplications. For example, the managed applications 310 (mail, browser,wrapped application) shown in the figure above are native applicationsthat execute locally on the device. Client agent 304 and applicationmanagement framework of this architecture act to provide policy drivenmanagement capabilities and features such as connectivity and SSO(single sign on) to enterprise resources/services 308. The client agent304 handles primary user authentication to the enterprise, for instanceto access gateway (AG) with SSO to other gateway server components. Theclient agent 304 obtains policies from gateway server 306 to control thebehavior of the managed applications 310 on the client device 302.

The Secure interprocess communication (IPC) links 312 between the nativeapplications 310 and client agent 304 represent a management channel,which allows client agent to supply policies to be enforced by theapplication management framework 314 “wrapping” each application. TheIPC channel 312 also allows client agent 304 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 308. Finally the IPC channel 312 allows theapplication management framework 314 to invoke user interface functionsimplemented by client agent 304, such as online and offlineauthentication.

Communications between the client agent 304 and gateway server 306 areessentially an extension of the management channel from the applicationmanagement framework 314 wrapping each native managed application 310.The application management framework 314 requests policy informationfrom client agent 304, which in turn requests it from gateway server306. The application management framework 314 requests authentication,and client agent 304 logs into the gateway services part of gatewayserver 306 (also known as NetScaler access gateway). Client agent 304may also call supporting services on gateway server 306, which mayproduce input material to derive encryption keys for the local datavaults 316, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the application management framework 314 “wraps” eachmanaged application 310. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 314 may “pair” with client agent 304 on first launch of anapplication 310 to initialize the Secure IPC channel and obtain thepolicy for that application. The application management framework 314may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the application 310.

The application management framework 314 may use services provided byclient agent 304 over the Secure IPC channel 312 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 316 (containers) may be also managed byappropriate interactions between the managed applications 310 and clientagent 304. Vaults 316 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 316 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 310 through access gateway 306. The applicationmanagement framework 314 is responsible for orchestrating the networkaccess on behalf of each application 310. Client agent 304 mayfacilitate these network connections by providing suitable time limitedsecondary credentials obtained following online authentication. Multiplemodes of network connection may be used, such as reverse web proxyconnections and end-to-end VPN-style tunnels 318.

The Mail and Browser managed applications 310 can have special statusand may make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAG logon. The Browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture can support the incorporation of various othersecurity features. For example, gateway server 306 (including itsgateway services) in some cases might not need to validate activedirectory (AD) passwords. It can be left to the discretion of anenterprise whether an AD password is used as an authentication factorfor some users in some situations. Different authentication methods maybe used if a user is online or offline (i.e., connected or not connectedto a network).

Step up authentication is a feature wherein gateway server 306 mayidentify managed native applications 310 that are allowed to have accessto more sensitive data using strong authentication, and ensure thataccess to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequested from the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 316 (containers) on the client device 302. The vaults 316 may beencrypted so that all on-device data including clipboard/cache data,files, databases, and configurations are protected. For on-line vaults,the keys may be stored on the server (gateway server 306), and foroffline vaults, a local copy of the keys may be protected by a userpassword or biometric validation. When data is stored locally on thedevice 302 in the secure container 316, it is preferred that a minimumof AES 256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 310 are logged and reported to the backend. Datawiping may be supported, such as if the application 310 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase or biometric data supplied by the user (ifoffline access is required). It may be XORed with another key randomlygenerated and stored on the server side if offline access is notrequired. Key Derivation functions may operate such that keys generatedfrom the user password use KDFs (key derivation functions, notablyPassword-Based Key Derivation Function 2 (PBKDF2)) rather than creatinga cryptographic hash of it. The latter makes a key susceptible to bruteforce or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector might cause multiple copies of thesame encrypted data to yield different cipher text output, preventingboth replay and cryptanalytic attacks. This may also prevent an attackerfrom decrypting any data even with a stolen encryption key. Further,authentication then decryption may be used, wherein application data isdecrypted only after the user has authenticated within the application.Another feature may relate to sensitive data in memory, which may bekept in memory (and not in disk) only when it's needed. For example,login credentials may be wiped from memory after login, and encryptionkeys and other data inside objective-C instance variables are notstored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented via the CEB, wherein after apolicy-defined period of inactivity, a user session is terminated.

Data leakage from the application management framework 314 may beprevented in other ways. For example, when an application 310 is put inthe background, the memory may be cleared after a predetermined(configurable) time period. When backgrounded, a snapshot may be takenof the last displayed screen of the application to fasten theforegrounding process. The screenshot may contain confidential data andhence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 320 without the use of an AD (active directory) 322 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 320 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 320. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 310 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want storefront to be accessed inthis manner. In this case, the client agent 304 may require the user toset a custom offline password and the AD password is not used. Gatewayserver 306 may provide policies to control and enforce passwordstandards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 310 as secondary credentials (for the purposeof accessing PKI protected web resources via the application managementframework micro VPN feature). For example, an application may utilizesuch a certificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from theclient agent 304 may be retrieved by gateway server 306 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in gateway server306.

Gateway server 306 may interact with an Enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 304 and the application management framework 314 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications, and ultimately by arbitrarywrapped applications (provided those applications use web service stylecommunication patterns where it is reasonable for the applicationmanagement framework to mediate https requests).

Application management client certificate support on iOS may rely onimporting a public-key cryptography standards (PKCS) 12 BLOB (BinaryLarge Object) into the iOS keychain in each managed application for eachperiod of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate might never be present in the iOSkeychain and might not be persisted except potentially in “online-only”data value that is strongly protected.

Mutual SSL or TLS may also be implemented to provide additional securityby requiring that a client device 302 is authenticated to theenterprise, and vice versa. Virtual smart cards for authentication togateway server 306 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 322, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when http (but not https) connections areproxied in VPN and MicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 310 is not running.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be service from one of several different locations in case offailure.

In some cases, managed applications 310 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 310 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is used, when an application reads a certificate for“who am I,” when an application uses the certificate to build a securesession token, and when an application uses private keys for digitalsigning of important data (e.g., transaction log) or for temporary dataencryption.

Referring now to FIG. 4, depicted is a block diagram of a system 400 ofan embedded browser. In brief overview, the system 400 may include aclient device 402 with a digital workspace for a user, a clientapplication 404, cloud services 408 operating on at least one networkdevice 432, and network applications 406 served from and/or hosted onone or more servers 430. The client application 404 can for instanceinclude at least one of: an embedded browser 410, a networking agent412, a cloud services agent 414, a remote session agent 416, or a securecontainer 418. The cloud services 408 can for instance include at leastone of: secure browser(s) 420, an access gateway 422 (or CIS, e.g., forregistering and/or authenticating the client application and/or user),or analytics services 424 (or CAS, e.g., for receiving information fromthe client application for analytics). The network applications 406 caninclude sanctioned applications 426 and non-sanctioned applications 428.

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 400 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the client device 402, the at least one network device 432and/or the one or more servers 430. The hardware includes circuitry suchas one or more processors in one or more embodiments. For example, theat least one network device 432 and/or the one or more servers 430 caninclude any of the elements of a computing device described above inconnection with at least FIG. 1 for instance.

The client device 402 can include any embodiment of a computing devicedescribed above in connection with at least FIG. 1 for instance. Theclient device 402 can include any user device such as a desktopcomputer, a laptop computer, a tablet device, a smart phone, or anyother mobile or personal device. The client device 402 can include adigital workspace of a user, which can include file system(s), cache ormemory (e.g., including electronic clipboard(s)), container(s),application(s) and/or other resources on the client device 402. Thedigital workspace can include or extend to one or more networksaccessible by the client device 402, such as an intranet and theInternet, including file system(s) and/or other resources accessible viathe one or more networks. A portion of the digital workspace can besecured via the use of the client application 404 with embedded browser410 (CEB) for instance. The secure portion of the digital workspace caninclude for instance file system(s), cache or memory (e.g., includingelectronic clipboard(s)), application(s), container(s) and/or otherresources allocated to the CEB, and/or allocated by the CEB to networkapplication(s) 406 accessed via the CEB. The secure portion of thedigital workspace can also include resources specified by the CEB (viaone or more policies) for inclusion in the secure portion of the digitalworkspace (e.g., a particular local application can be specified via apolicy to be allowed to receive data obtained from a networkapplication).

The client application 404 can include one or more components, such asan embedded browser 410, a networking agent 412, a cloud services agent414 (sometimes referred to as management agent), a remote session agent416 (sometimes referred to as HDX engine), and/or a secure container 418(sometimes referred to as secure cache container). One or more of thecomponents can be installed as part of a software build or release ofthe client application 404 or CEB, or separately acquired or downloadedand installed/integrated into an existing installation of the clientapplication 404 or CEB for instance. For instance, the client device maydownload or otherwise receive the client application 404 (or anycomponent) from the network device(s) 432. In some embodiments, theclient device may send a request for the client application 404 to thenetwork device(s) 432. For example, a user of the client device caninitiate a request, download and/or installation of the clientapplication. The network device(s) 432 in turn may send the clientapplication to the client device. In some embodiments, the networkdevice(s) 432 may send a setup or installation application for theclient application to the client device. Upon receipt, the client devicemay install the client application onto a hard disk of the clientdevice. In some embodiments, the client device may run the setupapplication to unpack or decompress a package of the client application.In some embodiments, the client application may be an extension (e.g.,an add-on, an add-in, an applet or a plug-in) to another application(e.g., a networking agent 412) installed on the client device. Theclient device may install the client application to interface orinter-operate with the pre-installed application. In some embodiments,the client application may be a standalone application. The clientdevice may install the client application to execute as a separateprocess.

The embedded browser 410 can include elements and functionalities of aweb browser application or engine. The embedded browser 410 can locallyrender network application(s) as a component or extension of the clientapplication. For instance, the embedded browser 410 can render aSaaS/Web application inside the CEB which can provide the CEB with fullvisibility and control of the application session. The embedded browsercan be embedded or incorporated into the client application via anymeans, such as direct integration (e.g., programming language or scriptinsertion) into the executable code of the client application, or viaplugin installation. For example, the embedded browser can include aChromium based browser engine or other type of browser engine, that canbe embedded into the client application, using the Chromium embeddedframework (CEF) for instance. The embedded browser can include aHTML5-based layout graphical user interface (GUI). The embedded browsercan provide HTML rendering and JavaScript support to a clientapplication incorporating various programming languages. For example,elements of the embedded browser can bind to a client applicationincorporating C, C++, Delphi, Go, Java, .NET/Mono, Visual Basic 6.0,and/or Python.

In some embodiments, the embedded browser comprises a plug-in installedon the client application. For example, the plug-in can include one ormore components. One such components can be an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the client application. For example,the client application can load and run an Active X control of theembedded browser, such as in a memory space or context of the clientapplication. In some embodiments, the embedded browser can be installedas an extension on the client application, and a user can choose toenable or disable the plugin or extension. The embedded browser (e.g.,via the plugin or extension) can form or operate as a secured browserfor securing, using and/or accessing resources within the securedportion of the digital workspace.

The embedded browser can incorporate code and functionalities beyondthat available or possible in a standard or typical browser. Forinstance, the embedded browser can bind with or be assigned with asecured container 418, to define at least part of the secured portion ofa user's digital workspace. The embedded browser can bind with or beassigned with a portion of the client device's cache to form a securedclipboard (e.g., local to the client device, or extendable to otherdevices), that can be at least part of the secured container 418. Theembedded browser can be integrated with the client application to ensurethat traffic related to network applications is routed through and/orprocessed in the client application, which can provide the clientapplication with real-time visibility to the traffic (e.g., whendecrypted through the client application). This visibility to thetraffic can allow the client application to perform or facilitatepolicy-based management (e.g., including data loss prevention (DLP)capabilities), application control, and collection and production ofanalytics.

In some embodiments, the embedded browser incorporates one or more othercomponents of the client application 404, such as the cloud servicesagent 414, remote session agent 416 and/or secure container 418. Forinstance, a user can use the cloud services agent 414 of the embeddedbrowser to interoperate with the access gateway 422 (sometimes referredto as CIS) to access a network application. For example, the cloudservices agent 414 can execute within the embedded browser, and canreceive and transmit navigation commands from the embedded browser to ahosted network application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

The client application 404 and CEB operate on the application layer ofthe operational (OSI) stack of the client device. The client application404 can include and/or execute one or more agents that interoperate withthe cloud services 408. The client application 404 can receive, obtain,retrieve or otherwise access various policies (e.g., an enterprise'scustom, specified or internal policies or rules) and/or data (e.g., froman access gateway 422 and/or network device(s) of cloud services 408, orother server(s), that may be managed by the enterprise). The clientapplication can access the policies and/or data to control and/or managea network application (e.g., a SaaS, web or remote-hosted application).Control and/or management of a network application can include controland/or management of various aspects of the network application, such asaccess control, session delivery, available features or functions,service level, traffic management and monitoring, and so on. The networkapplication can be from a provider or vendor of the enterprise (e.g.,salesforce.com, SAP, Microsoft Office 365), from the enterprise itself,or from another entity (e.g., Dropbox or Gmail service).

For example, the cloud services agent 414 can provide policy drivenmanagement capabilities and features related to the use and/or access ofnetwork applications. For example, the cloud services agent 414 caninclude a policy engine to apply one or more policies (e.g., receivedfrom cloud services) to determine access control and/or connectivity toresources such as network applications. When a session is establishedbetween the client application and a server 430 providing a SaaSapplication for instance, the cloud services agent 414 can apply one ormore policies to control traffic levels and/or traffic types (or otheraspects) of the session, for instance to manage a service level of theSaaS application. Additional aspects of the application traffic that canbe controlled or managed can include encryption level and/or encryptiontype applied to the traffic, level of interactivity allowed for a user,limited access to certain features of the network application (e.g.,print-screen, save, edit or copy functions), restrictions to use ortransfer of data obtained from the network application, limit concurrentaccess to two or more network applications, limit access to certain filerepositories or other resources, and so on.

The cloud services agent 414 can convey or feed information to analyticsservices 424 of the cloud services 408, such as information about SaaSinteraction events visible to the CEB. Such a configuration using theCEB can monitor or capture information for analytics without having aninline device or proxy located between the client device and theserver(s) 430, or using a SaaS API gateway ‘out-of-band’ approach. Insome embodiments, the cloud services agent 414 does not execute withinthe embedded browser. In these embodiments, a user can similarly use thecloud services agent 414 to interoperate with the access gateway (orCIS) 422 to access a network application. For instance, the cloudservices agent 414 can register and/or authenticate with the accessgateway (or CIS) 422, and can obtain a list of the network applicationsfrom the access gateway (or CIS) 422. The cloud services agent 414 caninclude and/or operate as an application store (or storefront) for userselection and/or downloading of network applications. Upon logging in toaccess a network application, the cloud services agent 414 can interceptand transmit navigation commands from the embedded browser to thenetwork application. The cloud services agent can use a remotepresentation protocol to display the output generated by the networkapplication to the embedded browser. For example, the cloud servicesagent 414 can include a HTML5 web client that allows end users to accessremote desktops and/or applications on the embedded browser.

In some embodiments, the cloud services agent 414 provides single signon (SSO) capability for the user and/or client device to access aplurality of network applications. The cloud services agent 414 canperform user authentication to access network applications as well asother network resources and services, by communicating with the accessgateway 422 for instance. For example, the cloud services agent 414 canauthenticate or register with the access gateway 422, to access othercomponents of the cloud services 408 and/or the network applications406. Responsive to the authentication or registration, the accessgateway 422 can perform authentication and/or SSO for (or on behalf of)the user and/or client application, with the network applications.

The client application 404 can include a networking agent 412. Thenetworking agent 412 is sometimes referred to as a software-defined widearea network (SD-WAN) agent, mVPN agent, or microVPN agent. Thenetworking agent 412 can establish or facilitate establishment of anetwork connection between the client application and one or moreresources (e.g., server 430 serving a network application). Thenetworking agent 412 can perform handshaking for a requested connectionfrom the client application to access a network application, and canestablish the requested connection (e.g., secure or encryptedconnection). The networking agent 412 can connect to enterpriseresources (including services) for instance via a virtual privatenetwork (VPN). For example, the networking agent 412 can establish asecure socket layer (SSL) VPN between the client application and aserver 430 providing the network application 406. The VPN connections,sometimes referred to as microVPN or application-specific VPN, may bespecific to particular network applications, particular devices,particular secured areas on the client device, and the like, forinstance as discussed above in connection with FIG. 3. Such VPNconnections can carry Microsoft Exchange traffic, Microsoft ActiveDirectory traffic, HyperText Transfer Protocol (HTTP) traffic, HyperTextTransfer Protocol Secure (HTTPS) traffic, as some examples.

The remote session agent 416 (sometimes referred to as HDX engine) caninclude features of the client agent 304 discussed above in connectionwith FIG. 2 for instance, to support display a remoting protocol (e.g.,HDX or ICA). In some embodiments, the remote session agent 416 canestablish a remote desktop session and/or remote application session inaccordance to any variety of protocols, such as the Remote DesktopProtocol (RDP), Appliance Link Protocol (ALP), Remote Frame Buffer (RFB)Protocol, and ICA Protocol. For example, the remote session agent 416can establish a remote application session for a user of the clientdevice to access an enterprise network application. The remote sessionagent 416 can establish the remote application session within or over asecure connection (e.g., a VPN) established by the networking agent 412for instance.

The client application or CEB can include or be associated with a securecontainer 418. A secure container can include a logical or virtualdelineation of one or more types of resources accessible within theclient device and/or accessible by the client device. For example, thesecure container 418 can refer to the entirety of the secured portion ofthe digital workspace, or particular aspect(s) of the secured portion.In some embodiments, the secure container 418 corresponds to a securecache (e.g., electronic or virtual clipboard), and can dynamicallyincorporate a portion of a local cache of each client device of a user,and/or a cloud-based cache of the user, that is protected or secured(e.g., encrypted). The secure container can define a portion of filesystem(s), and/or delineate resources allocated to a CEB and/or tonetwork applications accessed via the CEB. The secure container caninclude elements of the secure data container 228 discussed above inconnection with FIG. 2 for example. The CEB can be configured (e.g., viapolicies) to limit, disallow or disable certain actions or activities onresources and/or data identified to be within a secure container. Asecured container can be defined to specify that the resources and/ordata within the secure container are to be monitored for misuse, abuseand/or exfiltration.

In certain embodiments, a secure container relates to or involves theuse of a secure browser (e.g., embedded browser 410 or secure browser420) that implements various enterprise security features. Networkapplications (or web pages accessed by the secure browser) that areconfigured to run within the secure browser can effectively inherit thesecurity mechanisms implemented by the secure browser. These networkapplications can be considered to be contained within the securecontainer. The use of such a secure browser can enable an enterprise toimplement a content filtering policy in which, for example, employeesare blocked from accessing certain web sites from their client devices.The secure browser can be used, for example, to enable client deviceusers to access a corporate intranet without the need for a VPN.

In some embodiments, a secure container can support various types ofremedial actions for protecting enterprise resources. One such remedy isto lock the client device, or a secure container on the client devicethat stores data to be protected, such that the client device or securecontainer can only be unlocked with a valid code provided by anadministrator for instance. In some embodiments, these and other typesof remedies can be invoked automatically based on conditions detected onthe client device (via the application of policies for instance), or canbe remotely initiated by an administrator.

In some embodiments, a secure container can include a secure documentcontainer for documents. A document can comprise any computer-readablefile including text, audio, video, and/or other types of information ormedia. A document can comprise any single one or combination of thesemedia types. As explained herein, the secure container can help preventthe spread of enterprise information to different applications andcomponents of the client device, as well as to other devices. Theenterprise system (which can be partially or entirely within a cloudnetwork) can transmit documents to various devices, which can be storedwithin the secure container. The secure container can preventunauthorized applications and other components of the client device fromaccessing information within the secure container. For enterprises thatallow users to use their own client devices for accessing, storing, andusing enterprise data, providing secure container on the client deviceshelps to secure the enterprise data. For instance, providing securecontainers on the client devices can centralize enterprise data in onelocation on each client device, and can facilitate selective or completedeletion of enterprise data from each client device when desired.

The secure container can include an application that implements a filesystem that stores documents and/or other types of files. The filesystem can comprise a portion of a computer-readable memory of theclient device. The file system can be logically separated from otherportions of the computer-readable memory of the client device. In thisway, enterprise data can be stored in a secure container and privatedata can be stored in a separate portion of the computer-readable memoryof the client device for instance. The secure container can allow theCEB, network applications accessed via the CEB, locally installedapplications and/or other components of the client device to read from,write to, and/or delete information from the file system (if authorizedto do so). Deleting data from the secure container can include deletingactual data stored in the secure container, deleting pointers to datastored in the secure container, deleting encryption keys used to decryptdata stored in the secure container, and the like. The secure containercan be installed by, e.g., the client application, an administrator, orthe client device manufacturer. The secure container can enable some orall of the enterprise data stored in the file system to be deletedwithout modifying private data stored on the client device outside ofthe secure container. The file system can facilitate selective orcomplete deletion of data from the file system. For example, anauthorized component of the enterprise's system can delete data from thefile system based on, e.g., encoded rules. In some embodiments, theclient application can delete the data from the file system, in responseto receiving a deletion command from the enterprise's system.

The secure container can include an access manager that governs accessto the file system by applications and other components of the clientdevice. Access to the file system can be governed based on documentaccess policies (e.g., encoded rules) maintained by the clientapplication, in the documents and/or in the file system. A documentaccess policy can limit access to the file system based on (1) whichapplication or other component of the client device is requestingaccess, (2) which documents are being requested, (3) time or date, (4)geographical position of the client device, (5) whether the requestingapplication or other component provides a correct certificate orcredentials, (6) whether the user of the client device provides correctcredentials, (7) other conditions, or any combination thereof. A user'scredentials can comprise, for example, a password, one or more answersto security questions (e.g., What is the mascot of your high school?),biometric information (e.g., fingerprint scan, eye-scan), and the like.Hence, by using the access manager, the secure container can beconfigured to be accessed only by applications that are authorized toaccess the secure container. As one example, the access manager canenable enterprise applications installed on the client device to accessdata stored in the secure container and to prevent non-enterpriseapplications from accessing the data stored in the secure container.

Temporal and geographic restrictions on document access may be useful.For example, an administrator may deploy a document access policy thatrestricts the availability of the documents (stored within the securecontainer) to a specified time window and/or a geographic zone (e.g., asdetermined by a GPS chip) within which the client device must reside inorder to access the documents. Further, the document access policy caninstruct the secure container or client application to delete thedocuments from the secure container or otherwise make them unavailablewhen the specified time period expires or if the client device is takenoutside of the defined geographic zone.

Some documents can have access policies that forbid the document frombeing saved within the secure container. In such embodiments, thedocument can be available for viewing on the client device only when theuser is logged in or authenticated via the cloud services for example.

The access manager can also be configured to enforce certain modes ofconnectivity between remote devices (e.g., an enterprise resource orother enterprise server) and the secure container. For example, theaccess manager can require that documents received by the securecontainer from a remote device and/or sent from the secure container tothe remote device be transmitted through secured tunnels/connections,for example. The access manager can require that all documentstransmitted to and from the secure container be encrypted. The clientapplication or access manager can be configured to encrypt documentssent from the secure container and decrypt documents sent to the securecontainer. Documents in the secure container can also be stored in anencrypted form.

The secure container can be configured to prevent documents or dataincluded within documents or the secure container from being used byunauthorized applications or components of the client device or otherdevices. For instance, a client device application having authorizationto access documents from the secure container can be programmed toprevent a user from copying a document's data and pasting it intoanother file or application interface, or locally saving the document ordocument data as a new file outside of the secure container. Similarly,the secure container can include a document viewer and/or editor that donot permit such copy/paste and local save operations. Moreover, theaccess manager can be configured to prevent such copy/paste and localsave operations. Further, the secure container and applicationsprogrammed and authorized to access documents from the secure containercan be configured to prevent users from attaching such documents toemails or other forms of communication.

One or more applications (e.g., applications installed on the clientdevice, and/or network applications accessed via the CEB) can beprogrammed or controlled (e.g., via policy-based enforcement) to writeenterprise-related data only into the secure container. For instance, anapplication's source code can be provided with the resource name of thesecure container. Similarly, a remote application (e.g., executing on adevice other than the client device) can be configured to send data ordocuments only to the secure container (as opposed to other componentsor memory locations of the client device). Storing data to the securecontainer can occur automatically, for example, under control of theapplication, the client application, and/or the secure browser. Theclient application can be programmed to encrypt or decrypt documentsstored or to be stored within the secure container. In certainembodiments, the secure container can only be used by applications (onthe client device or a remote device) that are programmed to identifyand use the secure container, and which have authorization to do so.

The network applications 406 can include sanctioned network applications426 and non-sanctioned network applications 428. By way of anon-limiting example, sanctioned network applications 426 can includenetwork applications from Workday, Salesforce, Office 365, SAP, and soon, while non-sanctioned network applications 426 can include networkapplications from Dropbox, Gmail, and so on. For instance, FIG. 4illustrates a case where sanctioned applications 426 are accessed via aCEB. In operation (1), a user instance of a client application 404, thatis installed on client device 402, can register or authenticate with theaccess gateway 422 of cloud services 408. For example, the user canauthenticate the user to the client device and login to the clientdevice 402. The client application can automatically execute, or beactivated by the user. In some embodiments, the user can sign in to theclient application (e.g., by authenticating the user to the clientapplication). In response to the login or sign-in, the clientapplication can register or authenticate the user and/or the clientapplication with the access gateway 422.

In operation (2), in response to the registration or authentication, theaccess gateway 422 can identify or retrieve a list of enumerated networkapplications available or pre-assigned to the user, and can provide thelist to the client application. For example, in response to theregistration or authentication, the access gateway can identify the userand/or retrieve a user profile of the user. According to the identityand/or user profile, the access gateway can determine the list (e.g.,retrieve a stored list of network applications matched with the userprofile and/or the identity of the user). The list can correspond to alist of network applications sanctioned for the user. The access gatewaycan send the list to the client application or embedded browser, whichcan be presented via the client application or embedded browser to theuser (e.g., in a storefront user interface) for selection.

In operation (3), the user can initiate connection to a sanctionednetwork application (e.g., a SaaS application), by selecting from thelist of network applications presented to the user. For example, theuser can click on an icon or other representation of the sanctionednetwork application, displayed via the client application or embeddedbrowser. This user action can trigger the CEB to transmit a connectionor access request to a server that provisions the network application.The request can include a request to the server (e.g., SaaS provider) tocommunicate with the access gateway to authenticate the user. The servercan send a request to the access gateway to authenticate the user forexample.

In operation (4), the access gateway can perform SSO with the server, toauthenticate the user. For example, in response to the server's requestto authenticate the user, the access gateway can provide credentials ofthe user to the server(s) 430 for SSO, to access the selected networkapplication and/or other sanctioned network applications. In operation(5), the user can log into the selected network application, based onthe SSO (e.g., using the credentials). The client application (e.g., thenetworking agent 412 and/or the remote session agent 416) can establisha secure connection and session with the server(s) 430 to access theselected network application. The CEB can decrypt application trafficreceived via the secure connection. The CEB can monitor traffic sent viathe CEB and the secured connection to the servers 430.

In operation (6), the client application can provide information to theanalytics services 424 of cloud services 408, for analytics processing.For example, the cloud services agent 414 of the client application 404can monitor for or capture user interaction events with the selectednetwork application. The cloud services agent 414 can convey the userinteraction events to the analytics services 424, to be processed toproduce analytics.

FIG. 5 depicts an example embodiment of a system for using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 4, but that the client application (with embedded browser) is notavailable in the client device 402. A standard or typical browser may beavailable on the client device, from which a user can initiate a requestto access a sanctioned network application for instance. A networkapplication can be specified as being sanctioned or unsanctioned viapolicies that can be set by an administrator or automatically (e.g., viaartificial intelligence).

For example, in operation (1), the user may log into the networkapplication using the standard browser. For accessing a sanctionednetwork application, the user may access a predefined URL and/orcorresponding webpage of a server that provisions the networkapplication, via the standard browser, to initiate a request to accessthe network application. In some embodiments, the request can beforwarded to or intercepted by a designated gateway service (e.g., in adata path of the request). For example, the gateway service can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. In someembodiments, the access gateway can correspond to or include the gatewayservice. The gateway service can determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB. In some embodiments, there is no requirement for adesignated gateway service to detect or determine if the request isinitiated from a CEB, for example if the requested network applicationis sanctioned, that user is initiating the request via a standardbrowser, and/or that the predefined URL and/or corresponding webpage isaccessed.

In operation (2), the server may authenticate the user via the accessgateway of the cloud services 408. The server may communicate with theaccess gateway to authenticate the user, in response to the request. Forinstance, the request can include an indication to the server tocommunicate with the access gateway to authenticate the user. In someembodiments, the server is pre-configured to communicate with the accessgateway to authenticate the user, for requests to access a sanctionednetwork application. The server may send a request to the access gatewayto authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430.

In operation (3), the gateway service and/or the server can direct (orredirect) all traffic to a secure browser 420 which provides a securebrowsing service. This may be in response to at least one of: adetermination that the requested network application is a sanctionednetwork application, a determination that the request is initiated froma source other than a CEB, a determination that the requested networkapplication is sanctioned, a determination that user is initiating therequest via a standard browser, and/or a determination that thepredefined URL and/or corresponding webpage is accessed.

The user's URL session can be redirected to the secure browser. Forexample, the server, gateway service and/or the access gateway cangenerate and/or send a URL redirect message to the standard browser,responsive to the determination. The secure browser plug-in of thestandard browser can receive the URL redirect message, and can forexample send a request to access the non-sanctioned network application,to the secure browser 420. The secure browser 420 can direct the requestto the server of the non-sanctioned network application. The URLredirect message can instruct the standard browser (and/or the securebrowser plug-in) to direct traffic (e.g., destined for the networkapplication) from the standard browser to the secure browser 420 hostedon a network device. This can provide clientless access and control viadynamic routing though a secure browser service. In some embodiments, aredirection of all traffic to the secure browser 420 is initiated orconfigured, prior to performing authentication of the user (e.g., usingSSO) with the server.

In some embodiments, the gateway service can direct or request theserver of the requested network application to communicate with thesecure browser 420. For example, the gateway service can direct theserver and/or the secure browser to establish a secured connectionbetween the server and the secure browser, for establishing anapplication session for the network application.

In some embodiments, the secured browser 420 comprises a browser that ishosted on a network device 432 of the cloud services 408. The securedbrowser 420 can include one or more features of the secured browser 420described above in connection with at least FIG. 4 for instance. Thehosted browser can include an embedded browser of a CEB that is hostedon the network device 432 instead of on the client device. The hostedbrowser can include an embedded browser of a hosted virtualized versionof the CEB that is hosted on the network device 432. Similar to the CEBinstalled on the client device, traffic is routed through the CEB hostedon the network device, which allows an administrator to have visibilityof the traffic through the CEB and to remain in control for securitypolicy control, analytics, and/or management of performance.

FIG. 6 illustrates an example implementation for browser redirectionusing a secure browser plug-in. In brief overview, the implementationincludes a web browser 512 with a secure browser plug-in 516 operatingon a client device, and a hosted web browser (or secure browser) 522residing on a network device. The web browser 512 can correspond to astandard browser, instead of an embedded browser as discussed above inconnection with FIG. 4 for example. The secure browser plug-in 516 canexecute within a first network 510 and access a server 430 in a secondnetwork 530. The first network 510 and the second network 530 are forillustration purposes and may be replaced with fewer or additionalcomputer networks. A secure browser plug-in 516 can be installed on thestandard browser 512. The plug-in can include one or more components.One such component can include an ActiveX control or Java control or anyother type and/or form of executable instructions capable of loadinginto and executing in the standard browser. For example, the standardbrowser can load and run an Active X control of the secure browserplug-in 516, in a memory space or context of the standard browser. Insome embodiments, the secure browser plug-in can be installed as anextension on the standard browser, and a user can choose to enable ordisable the plugin or extension. The secure browser plug-in cancommunicate and/or operate with the secured browser 420 for securing,using and/or accessing resources within the secured portion of thedigital workspace.

By using the secure browser plug-in 516 operating within the standardbrowser 512 network applications accessed via the standard browser 512can be redirected to a hosted secure browser. For instance, the securebrowser plug-in 516 can be implemented and/or designed to detect that anetwork application is being accessed via the standard browser, and candirect/redirect traffic from the client device associated with thenetwork application, to the hosted secure browser. The hosted securebrowser can direct traffic received from the network application, to thesecure browser plug-in 516 and/or a client agent 514 for renderingand/or display for example. The client agent 514 can execute within theweb browser 512 and/or the secure browser plug-in, and can includecertain elements or features of the client application 404 discussedabove in connection with at least FIG. 4 for example. For instance, theclient agent 514 can include a remote session agent 416 for renderingthe network application at the web browser 512. In some embodiments, thenetwork application is rendered at the hosted secure browser, and therendered data is conveyed or mirrored to the secure browser plug-in 516and/or the client agent 514 for processing and/or display.

By way of an example, a user may be working remotely and may want toaccess a network application that is internal to a secure corporatenetwork while the user is working on a computing device connected to anunsecure network. In this case, the user may be utilizing the standardbrowser 512 executing in the first network 510, in which the firstnetwork 510 may comprise an unsecure network. The server 430 that theuser wants to access may be on the second network 530, in which thesecond network 530 comprises a secure corporate network for instance.The user might not be able to access the server 430 from the unsecurefirst network 510 by clicking on an internal uniform record locator(URL) for the secure website 532. That is, the user may need to utilizea different URL (e.g., an external URL) while executing the standardbrowser 512 from the external unsecure network 510. The external URL maybe directed to or may address one or more hosted web browsers 522configured to access server(s) 430 within the second network 530 (e.g.,secure network). To maintain secure access, the secure browser plug-in516 may redirect an internal URL to an external URL for a hosted securebrowser.

The secure browser plug-in 516 may be able to implement networkdetection in order to identify whether or not to redirect internal URLsto external URLs. The standard browser 512 may receive a requestcomprising an internal URL for a website executing within the securenetwork. For example, the standard browser 512 may receive the requestin response to a user entering a web address (e.g., for secure website532) in the standard browser. The secure browser plug-in 516 mayredirect the user web browser application 512 from the internal URL toan external URL for a hosted web browser application. For example, thesecure browser plug-in 516 may replace the internal URL with an externalURL for the hosted web browser application 522 executing within thesecure network 530.

The secure browser plug-in 516 may allow the client agent 514 to beconnected to the hosted web browser application 522. The client agent514 may comprise a plug-in component, such as an ActiveX control or Javacontrol or any other type and/or form of executable instructions capableof loading into and executing in the standard browser 512. For example,the client agent 514 may comprise an ActiveX control loaded and run by astandard browser 512, such as in the memory space or context of the userweb browser application 512. The client agent 514 may be pre-configuredto present the content of the hosted web browser application 522 withinthe user web browser application 512.

The client agent 514 may connect to a server or the cloud/hosted webbrowser service 520 using a thin-client or remote-display protocol topresent display output generated by the hosted web browser application522 executing on the service 520. The thin-client or remote-displayprotocol can be any one of the following non-exhaustive list ofprotocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

The hosted web browser application 522 may navigate to the requestednetwork application in full-screen mode, and can render the requestednetwork application. The client agent 514 may present the content orrendition of the network application on the web browser application 512in a seamless and transparent manner such that it appears that thecontent is being displayed by the standard browser 512, e.g., based onthe content being displayed in full screen mode. In other words, theuser may be given the impression that the website content is displayedby the user web browser application 512 and not by the hosted webbrowser application 522. The client agent 514 may transmit navigationcommands generated by the user web browser application 512 to the hostedweb browser application 522 using the thin-client or remote-displayprotocol. Changes to the display output of the hosted web browserapplication 522, due to the navigation commands, may be reflected in theuser web browser application 512 by the client agent 514, giving theimpression to the user that the navigation commands were executed by theuser web browser application 512.

Referring again to FIG. 5, and in operation (4), a new browser tab canopen on the standard browser, to render or display the secure browsersession. The new browser tab can be established or opened by the securebrowser plug-in for instance. The secure browser plug-in and/or a clientagent can receive data from the secure browser session, and can renderthe network application within the new browser tab as discussed above inconnection with FIG. 6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

FIG. 7 depicts another example embodiment of a system of using a securebrowser. In brief overview, the system includes cloud services 408,network applications 406 and the client device 402. In some embodiments,various elements of the system are similar to that described above forFIG. 5. A client application with embedded browser is not available inthe client device 402. A standard or typical (e.g., HTML5) browser isavailable on the client device, from which a user can initiate a requestto access a non-sanctioned network application. A network applicationcan be specified as being sanctioned or non-sanctioned via policies thatcan be set by an administrator or automatically (e.g., via artificialintelligence).

In operation (1), the user may attempt to log into a non-sanctionednetwork application using the standard browser. The user may attempt toaccess a webpage of a server that provisions the network application,and to initiate a request to access the network application. In someembodiments, the request can be forwarded to or intercepted by adesignated gateway service (e.g., in a data path of the request). Forexample, the gateway service (sometimes referred to as SWG) can resideon the client device (e.g., as an executable program), or can reside ona network device 432 of the cloud services 408 for instance. The gatewayservice can detect or otherwise determine if the requested networkapplication is a sanctioned network application. The gateway service candetermine if a CEB initiated the request. The gateway service can detector otherwise determine that the request is initiated from a source(e.g., initiated by the standard browser) in the client device otherthan a CEB.

In operation (2), the gateway service detects that the requested networkapplication is a non-sanctioned network application. The gateway servicecan for instance extract information from the request (e.g., destinationaddress, name of the requested network application), and compare theinformation against that from a database of sanctioned and/ornon-sanctioned network applications. The gateway service can determine,based on the comparison, that the requested network application is anon-sanctioned network application.

In operation (3), responsive to the determination, the gateway servicecan block access to the requested network application, e.g., by blockingthe request. The gateway service can generate and/or send a URL redirectmessage to the standard browser, responsive to the determination. TheURL redirect message can be similar to a URL redirect message sent fromthe server to the standard browser in FIG. 5 in operation (3). A securebrowser plug-in of the standard browser can receive the URL redirectmessage, and can for example send a request to access the non-sanctionednetwork application, to the secure browser 420. The secure browser 420can direct the request to the server of the non-sanctioned networkapplication.

The server of the non-sanctioned network application may authenticatethe user via the access gateway of the cloud services 408, e.g.,responsive to receiving the request from the secure browser. The servermay communicate with the access gateway to authenticate the user, inresponse to the request. The server may send a request to the accessgateway to authenticate the user. In response to the server's request toauthenticate the user, the access gateway can provide credentials of theuser to the server 430. Upon authentication, the secure browser (or acorresponding CEB) can establish a secured connection and an applicationsession with the server.

In operation (4), a new browser tab can open on the standard browser, torender or display the secure browser's application session. The newbrowser tab can be established or opened by the secure browser plug-infor instance. The secure browser plug-in and/or a client agent canreceive data from the secure browser session, and can render the networkapplication within the new browser tab as discussed above in connectionwith FIGS. 5-6 for instance.

In operation (5), the secure browser can feed all user interactionevents via the network application, back to analytics service forprocessing. The secure browser plug-in can monitor for and intercept anyuser interaction events directed to the rendition of the networkapplication within the browser tab. Hence, a user can use a native (orstandard) browser to access a network application while allowingvisibility into the network application's traffic, via theinteroperation of cloud services and a secure browser (in the absence ofthe client application).

In some embodiments, in the absence or non-availability of a CEB on theclient device, browser redirection is performed so that each requestednetwork application is accessed via a corresponding hosted securebrowser (or hosted CEB) for handling, instead of having all trafficredirected through a single hosted secure browser (or hosted CEB). Eachdedicated secure browser can provide compartmentalization and improvedsecurity.

The use of a CEB, whether hosted or local to the client device, canallow for end-to-end visibility of application traffic for analytics,service level agreement (SLA), resource utilization, audit, and so on.In addition to such visibility, the CEB can be configured with policiesfor managing and controlling any of these as well as other aspects. Forexample, DLP features can be supported, to control “copy and paste”activities, download of files, sharing of files, and to implementwatermarking for instance. As another example, the CEB can be configuredwith policies for managing and controlling access to local drives and/ordevice resources such as peripherals.

Referring now to FIG. 8, an example embodiment of a system for usinglocal embedded browser(s) and hosted secured browser(s) is depicted. Anenvironment is shown where different types of client devices 402A, 402Bmay be used (e.g., in a BYOD context), such that one may be locallyequipped with a suitable CEB, and another client device may not have asuitable local CEB installed. In such an environment, systems describedin FIGS. 4, 5 and 7 can be used to support each of the client devicesbased on the availability of a locally installed and suitable CEB.

FIG. 9 depicts an example process flow for using local embeddedbrowser(s) and hosted secured browser(s). The process flow can be usedin the environment described above in FIG. 8, to determine whether anembedded browser or a hosted secured browser should be used for eachclient device to access a network application. For example, in operation901, a HTTP client can attempt to access a web service (e.g., server ofa network application). In operation 903, the web service can redirectthe HTTP client to a gateway service for authentication. In operation905, the gateway service can determine if the HTTP client is a CEB. Ifso, in operation 909, the gateway service can determine if the CEB is asuitable CEB, e.g., capable of enforcing defined application policies.If so, in operation 911, the CEB is allowed access to the web service,and can enforce the defined policies.

If the gateway service determines that the HTTP client is not a CEB, thegateway service can cause a virtualized version of a CEB to beinitialized and hosted on a remote server (e.g., a network device 432 ofcloud services 408), in operation 907. In some embodiments, such ahosted CEB may already be available on a network device 432, and can beselected for use. For example in operation 911, the CEB is allowedaccess to the web service, and can enforce the defined policies.

If the gateway service determines that the HTTP client is a CEB, butthat the CEB is not a suitable CEB, the gateway service can cause avirtualized version of a CEB to be initialized and hosted on a remoteserver (e.g., a network device 432 of cloud services 408), in operation907. In some embodiments, such a hosted CEB may already be available ona network device 432, and can be selected for use. For example inoperation 911, the CEB is allowed access to the web service, and canenforce the defined policies.

In some embodiments, if the user is requesting access to a webapplication located in a company data center, the gateway service (incloud service or on premise) can allow access when the clientapplication with CEB is detected. Otherwise, the request can be routedto a service with the hosted virtualized version of the CEB, and thenaccess is authenticated and granted.

At operation 905 and/or operation 909 for instance, the decisions madeon whether the HTTP client is a CEB and whether it is a suitable CEB maybe determined by a number of factors. For example, to determine if theHTTP client is CEB, the gateway service may take into account factors,for example including at least one of: user Identity and strength ofauthentication, client Location, client IP Address, how trusted the useridentity, client location, client IP are, jailbreak status of the clientdevice, status of anti-malware software, compliance to corporate policyof the client device, and/or remote attestation or other evidence ofintegrity of the client software.

To determine if the CEB is able to honor or support all definedapplication policies (which may vary by client version, client OSplatform and other factors), the client device's software and gatewayservice may perform capability negotiation and/or exchange versioninformation. In some embodiments, the gateway service can query or checka version number or identifier of the CEB to determine if the CEB is asuitable CEB to use.

Driving all the traffic though the CEB then allows additional control ofcontent accessing SaaS and Web based systems. Data Loss Prevention (DLP)of SaaS and Web traffic can be applied through the CEB app with featuresincluding copy and paste control to other CEB access applications or ITmanaged devices. DLP can also be enforced by enabling content to bedownloaded only to designated file servers or services under IT control.

Referring now to FIG. 10, depicted is an example embodiment of a systemfor managing user access to webpages. Some webpages (or websites) areknown to be safe while others may be suspect. A user may access awebpage via a corresponding URL through a standard browser. For example,the user may click on a link corresponding to the URL, which may beincluded in an email being viewed using a mail application. An accessgateway (SWG) may intercept an access request generated by the clickingof the link, and can determine if the corresponding URL is safe orsuspect. If the URL is known to be safe, the access gateway can allowthe request to proceed to the corresponding website or web server. Ifthe URL is suspect, the access gateway can redirect the request to behandled via a hosted secure browser. The secure browser can requestaccess for, and access the webpage (on behalf of the standard browser),and can allow the webpage information to be conveyed to the standardbrowser, similar to the handling of a network application via browserredirection as discussed in connection with at least FIGS. 7 and 5.

C. Systems and Methods for Delivering a Network Application

The present disclosure is directed towards systems and methods fordelivering a network application. An intermediary device (sometimesreferred to herein as a Netscaler device or network appliance) mayinclude an HDX engine (also referred to herein as a remote sessionagent). The remote session agent may process remote session traffic, atthe intermediary device using a System on Chip (or other processor orcomputing device of the intermediary device), for provisioning hostedapplications or desktops to a client device. In this regard, a receiverapplication (also referred to herein as a client application) canreceive and render the processed remote session traffic, and may nothave to further process or decode the processed remote session trafficprior to rendering at the client device. In a similar manner, contentprovided via a web, remotely-hosted, or SaaS application may beprocessed or decoded at the intermediary device. For instance, theprocessed content may correspond to bitmap data, raw audio data,cascaded style sheet (CSS) files (or similar files), etc. The bitmapdata, raw audio data, CSS files, etc. may be transmitted from theintermediary device to the client device for rendering (e.g., withoutfurther processing or decoding).

In some instances, client devices may be connected to an intermediarydevice via a Wide Area Network (WAN). Also, the intermediary device maybe connected to a server via a Local Area Network (LAN). Due to thegreater distances and/or complexity in conveying traffic from theintermediary device to a client device, much traffic processing isperformed at the client device to manage or improve the performance ofnetwork applications remotely provisioned to the client device, asexperienced by a user. For instance, the client device may decode andrender various remotely-hosted application session traffic and webtraffic. Due to the significant processing load and heavy-lifting on theclient device, applications which may be native or hosted on the clientdevice may experience reduced performance. Client-side processing aredependent on the particular processing capabilities of client devices ofdifferent types or forms, leading to inconsistent or varying performanceand user experience across different client devices (e.g., for the samenetwork application). As an example, user experience may varysignificantly across different platforms and even browsers (e.g., forweb applications).

As computing systems are moved to cloud-based computing systems, theaforementioned configuration may be reversed (e.g., to have a LANconnection between client devices and an intermediary device, and a WANconnection between the intermediary device and the server). In someinstances, the intermediary device may be located on premises (e.g.,near or in a same location as the client device), and a virtual deliveryagent (VDA) is in the cloud. In these instances, embodiments of thepresent systems and methods allow for processing to be performed at theintermediary device, as optimization needs may be greater between theintermediary device and the VDA. With the processing (of remote-hostedsession traffic and web-encoded data) being offloaded to theintermediary device, the intermediary device can communicate processeddata/traffic to the client device for final rendering with minimal or nofurther processing.

According to the embodiments described herein, network devices (forinstance, network printers), may receive requests (e.g., print jobs)from the intermediary device, which is not easily accomplished accordingto the current designs and implementations. For example, theintermediary device, having processed or decoded traffic of networkapplication data locally at the intermediary device, can convey thedecoded data directly to a network printer for printing (e.g., withoutfurther decoding or processing at the network printer). In contrast, aVDA residing at a host server (e.g., that hosts a network application)may not be able to direct encoded traffic (from the network application)to a network printer for printing.

Furthermore, graphics decoding capabilities may become more consistentwhen centralized on an intermediary device, and be less affected acrossclient device platforms, as the intermediary device handles decoding andprovides the final output to the client device for rendering. Forinstance, audio and graphics decoding and/or optimization (and sometimesrendering) may be performed at the intermediary device, and the raw (oroptimized, better quality) audio and graphics can be sent to the clientdevice for rendering. In this regard, the user is provided with a betteror more consistent audio/graphics experience irrespective of theplatform and the type of client device. Also, the intermediary devicecan host or execute a secure browser which provides a secure browserservice for web or SaaS applications for instance. Therefore,potentially unsecure content may be provided via the secure browserservice to the user, which the user may not otherwise have access to inother implementations and configurations. In some embodiments, theintermediary device may maintain a session state of a networkapplication accessed by the client device, when the user switches accessfrom one client device to another client device, and/or when the userdisconnects from and re-connects to the same session of the networkapplication.

Referring to FIG. 11, depicted is a block diagram of one embodiment of asystem 1100 for delivering a network application. The system 1100 mayinclude one or more servers 1102 which host one or more networkapplication(s) 1108, a client device 1104 executing a client application1116, and an intermediary device 1106 located between the server(s) 1102and the client device 1104. The intermediary device 1106 can include anetworking agent 1110 for establishing a connection between theserver(s) 1102 and the intermediary device 1106. The intermediary device1106 can include a remote session agent 1112 for exchanging data betweenthe network applications 1108 hosted on the server(s) 1102, and theintermediary device 1106. In some instances, the data from the networkapplications 1108 may be encoded. The intermediary device 1106 canincludes a system on chip (SoC) 1114 that can decode the encodedapplication data from the network applications 1108 executing orotherwise hosted on the server(s) 1102. The networking agent 1110 mayestablish a connection with the client device 1104. The remote sessionagent 1112 may communicate the decoded data to the client device 1104for rendering within the client application 1116. The client device 1104may render the decoded data without further processing at (or on/within)the client device 1104.

Each of the above-mentioned elements or entities is implemented inhardware, or a combination of hardware and software, in one or moreembodiments. Each component of the system 1100 may be implemented usinghardware or a combination of hardware or software detailed above inconnection with FIG. 1. For instance, each of these elements or entitiescan include any application, program, library, script, task, service,process or any type and form of executable instructions executing onhardware of the client device 1104, server 1102 and/or intermediarydevice 1106, for instance. The hardware includes circuitry such as oneor more processors in one or more embodiments.

The server(s) 1102 may execute, provide, provision, and/or host one ormore network application(s) 1108. The network application 1108 mayinclude any type or form of network application 406 described above inconnection with at least FIGS. 2-5, 7, and 8. The server(s) 1102 mayinclude any embodiment of volatile memory 122 or non-volatile memory 128(discussed in FIG. 1 for example) which may store the networkapplications 1108, and may communicate with other various components ofthe system 1100 via a communications interface 118. Hence, the server(s)1102 may be similar in some aspects to the computer 101 described withreference to FIG. 1. A network application 1108 may be accessed by theclient device 1104 via a remote-hosted session of the networkapplication provisioned via the intermediary device 1106.

A networking agent 1110 may establish a network connection between theserver(s) 1102 and the intermediary device 1106. In some embodiments,the networking agent 1110 may include one or more elements ofembodiments of the networking agent 412 described above in reference toFIGS. 4 and 8. The client device 1104 may execute (e.g., via one or moreof the computing components depicted in FIG. 1) a client application1116 that can render information from a network application 1110. Theclient device 1104 may be similar in some aspects to the client device402 described with reference to FIGS. 4, 5, 7, and 8. A remote sessionagent 1112 of the intermediary device 1106 may receive/retrieveapplication data from the network application 1108 hosted on/at theserver(s) 1102. The intermediary device 1106 may include the SoC 1114.The SoC 1114 may be configured to decode data from the networkapplications 1108 to be rendered on the client device 1104 via theclient application 1112, as discussed below. It is noted that, while thenetworking agent 1110 and remote session agent 1112 are representedwithin the intermediary device 1106, in some embodiments, the networkingagent 1110 and/or remote session agent 1112 may be located at theserver(s) 1102. In some embodiments, the system 1110 may include anetworking agent and remote session agent corresponding to the networkconnection between the server(s) 1102 and intermediary device 1106, anda networking agent and remote session agent corresponding to the networkconnection between the intermediary device 1106 and the client device1104.

In some embodiments, the client application 1112 may include one or moreelements of any embodiment of the client application 404 described abovein connection with at least FIGS. 4 and 8. In some embodiments, theclient application 1112 may include an embedded browser. The clientapplication 1112 with the embedded browser (CEB) can include any elementor embodiment of a CEB as previously described above in connection withat least FIGS. 4 and 8. In some embodiments, the client application 1112may execute on a client device 1104 operated by a user. The clientdevice 1104 may include one or more elements of any embodiment of theclient device 402 described above in connection with at least FIGS. 4,5, 7, and 8.

The intermediary device 1106 may be designed or implemented to establishconnection(s) with the network application(s) 1108 on the server(s)1102. In some embodiments, the intermediary device 1106 may include anetworking agent 1110. The networking agent 1110 may establish, create,generate, or otherwise form one or more connections between theserver(s) 1102 and the intermediary device 1106. As stated above, whilethe networking agent 1110 is shown as being located at/on/within theintermediary device 1106, in some embodiments, the networking agent 1110may be located at/on/within the server(s) 1102.

The networking agent 1110 is sometimes referred to as an SD-WAN agent,mVPN agent, or microVPN agent. The networking agent 1110 can establishor facilitate establishment of a network connection between theintermediary device 1106 and the server(s) 1102 (which hosts and/orexecutes the network applications 1108). The networking agent 1110 canperform handshaking for a requested connection from the intermediarydevice 1106 (or client device 1104) to access a network application, andcan establish the requested connection. In some embodiments, thenetworking agent 1110 may establish a secure or encrypted connection.For instance, the networking agent 1110 may connect to enterpriseresources (including services and network applications 1108) forinstance via a virtual private network (VPN). For example, thenetworking agent 1110 can establish a secure socket layer (SSL) VPNbetween the intermediary device 1106 and the server(s) 1102, which cansupport remote delivery or provisioning of one or more networkapplications 1108. The VPN connections, sometimes referred to asmicroVPN or application-specific VPN, may be specific to particularnetwork applications, particular devices, particular secured areas onthe client device, and the like, for instance as discussed above inconnection with FIG. 3. Such VPN connections can carry MicrosoftExchange traffic, Microsoft Active Directory traffic, HyperText TransferProtocol (HTTP) traffic, HyperText Transfer Protocol Secure (HTTPS)traffic, as some examples.

In some embodiments, the networking agent 1110 may be designed orimplemented to form an HTTP or web-based session with the server(s)1102. The networking agent 1110 may establish a transmission controlprotocol (TCP) connection to the server 1102 (e.g., a port of the server1102). The networking agent 1110 can exchange various commands with theserver 1102 within the HTTP session in accordance with TCP. In someembodiments, the networking agent 1110 may establish a secure HTTP(e.g., HTTPS) session in a manner similar to the secure connectionsdescribed above.

In these embodiments, the networking agent 1110 can form or establishthe network connection between the server(s) 1102 and the intermediarydevice 1106. In some embodiments, the networking agent 1110 may form orestablish a secure connection (e.g., SSL VPN connection) between theserver(s) 1102 and the intermediary device 1106.

The intermediary device 1106 may be designed or implemented to initiatea provisioning session to deliver a remotely-hosted application ordesktop session. The intermediary device 1106 may initiate theprovisioning session within or across the network connection establishedby the networking agent 1110. In some embodiments, the remote sessionagent 1112 may initiate the provisioning session (e.g., which may beestablished using Citrix high definition user experience (HDX) orindependent computing architecture (ICA) protocol, or remote desktopprotocol (RDP)). The provisioning session and/or network connection caninclude a plurality of virtual channels for communicating one or moretypes of application data (e.g., audio, graphics, metadata, printerdata, disk data, smart card data, and so on) to the intermediary device.For instance, some types of application data can each be conveyed orcommunication via a dedicated virtual channel within the provisioningsession, and/or certain types of application data can each be conveyedor communication to the intermediary device by sharing one or morevirtual channels. A virtual channel can correspond to or include aclient-side virtual driver that communicates with a server-sideapplication. A virtual channel can provide a secure connection tocommunicate between devices and/or applications. On the client side,virtual channels can correspond to virtual drivers each providing aspecific function. The virtual drivers can operate at the presentationlayer protocol level. There can be a number of these protocols active atany given time by multiplexing channels that are provided by forinstance the WinStation protocol layer. Multiple virtual channels can becombined or multiplexed within a provisioning session (e.g., an ICA-HDXsession or traffic stream).

The remote session agent 1112 may initiate the provisioning session inaccordance with any type or form of protocols, such as RDP, ApplianceLink Protocol (ALP), Remote Frame Buffer (RFB) Protocol, and ICAProtocol. Such protocols can allow user interface (UI) elements of anapplication or desktop session (or other application data from thenetwork applications 1108) that is natively hosted on the server(s)1102, to be generated at the server(s) 1102 and provisioned to a clientdevice for instance. The UI elements and other application data may beencoded within the server(s) 1102 using such protocols to form encodedapplication data or traffic, which is then delivered or otherwiseprovisioned to the intermediary device 1106. Hence, the server(s) 1102may generate the application data and then encode the application dataprior to providing the application data to the intermediary device 1106.In some embodiments, the server(s) 1102 may generate the applicationdata in an encoded format (sometimes referred as encoded applicationdata) which is provided to the intermediary device 1106.

In some embodiments, at least one of the network applications 1108 maycorrespond to a remote-hosted desktop, a remote-hosted application, or asoftware-as-a-service (SaaS) application. A remote-hosted desktop may bea virtual desktop hosted on the server 1102 which is accessed by orremotely provisioned to the client device 1104. In some embodiments, thedelivery of a remote-hosted desktop may be via a HDX-based, ICA-based,RDP-based, etc., session and/or connection, as described above. Aremote-hosted application may be an application which is installed on/inthe remote-hosted desktop environment and is therefore accessible withinthe remote-hosted desktop. A SaaS application is a centrally-hostedapplication which is typically accessible on a subscription basis. Insome embodiments, the SaaS applications may be web-based applications.In other embodiments, the SaaS applications may correspond toremote-hosted applications and, therefore, can be delivered inHDX/ICA/RDP-based sessions and/or connections.

The intermediary device 1106 may be designed or implemented to transmit,receive, exchange, or otherwise communicate with the networkapplications 1108 via the network connection established by thenetworking agent 1110. In some embodiments, the remote session agent1112 may communicate with the network applications 1108 across thenetwork connection formed by the networking agent 1110. The networkapplications 1108 hosted on the server(s) 1102 may create, generate,produce, populate, compile, or otherwise form application data forrendering at the client device 1104 (e.g., within the client application1116). The application data may be usable (or include information orcommands) to generate a user interface (UI) for the network application1108 (e.g., at the client device 1104). The application data may be datacorresponding to UI commands. The UI commands may be commands forforming widgets or other elements of the UI (e.g., size, location, type,visual characteristics). In some embodiments, the application data mayinclude control or configuration traffic for regulating various trafficcharacteristics of communications from the server(s) 1102, such as datarate, service level agreements, etc. In some embodiments, theapplication data can include application session state, various userprofile information, user-generated data, cache data, etc. In someembodiments, the application data may include graphics and/or audiodata. In some embodiments, the application data may include networkdevice instructions.

In some embodiments, the network applications 1108 may generate theapplication data in an encoded format. Encoded data (or variationsthereof, such as encode data, encoding data, etc.), as used herein, canrefer to a data format or structure which is accessible by particularapplications or software that have the capability to decode the dataformat or structure. Thus, encoded application data is not “raw,” orrenderable data (e.g., decoded data) that can be rendered or accessedindependent of such a decoding capability. Rather, encoded applicationdata should be decoded prior to being renderable at a device orendpoint. In some embodiments, the network applications 1108 may encodethe application data in a format which is accessible by networkapplication-specific software. For instance, the application data may bein an encoded format which is decoded into cascading style sheet (CSS)files that can then be rendered as a user interface for the networkapplication.

Other various examples and/or types of encoded data can includecompressed graphic, image or video data (Codec), compressed audio data,etc. The encoded application data may have various file formats (orcontainers) such as, for instance, audio-video interleave (AVI), flashvideo format (FLV), Windows media video (WMV), Apple QuickTime movie(MOV), Moving Pictures Expert Group 4 (MP4), joint photographic expertsgroup (JPEG), tagged image file format (TIFF), graphics interchangeformat (GIF), computer graphics metafile (CGM), waveform audio fileformat (WAV), audio interchange file format (AIFF), MPEG-1 Audio Layer 3(MP3), advanced audio coding (AAC), Microsoft Word document (DOC),Office open XML document (DOCX), ASCII text as comma-separated values(CSV), etc.

In some embodiments, the encoded application data may include encodeduser interface display commands or messages (e.g., in HDX or ICAprotocol, for instance). The encoded application data may be a specificformat of commands or messages which correspond to variouscharacteristics of user interface widgets similar to CSS files (e.g.,e.g., size, location, type, visual characteristics). Decoded applicationdata in these examples may include CSS files which are renderable toproduce graphics in raw from (e.g., bitmap or other raw graphics data)which is displayed or rendered without further processing. Otherexamples of decoded application data can include plain text, raw audiodata, etc.

In each of these examples, the encoded application data uses a specificdecoder, which may be file format or container-specific, for decodingthe application data for rendering (e.g., at the client device 1104)without further processing. Hence, the decoded application data is in arenderable format at the client device 1104. For instance, the decodedapplication data may be CSS files and various style elements. The CSSfiles and various style elements from the decoded application data maybe used to render the user interface for the network application 1108.

The intermediary device 1106 may be designed or implemented to receiveencoded traffic from the network applications 1108. The intermediarydevice 1106 may receive the encoded application data from the networkapplication(s) 1108 on the server(s) 1102 via the network connectionestablished by the networking agent 1110. The remote session agent 1112of the intermediary device 1106 may receive or access the encodedapplication data. For instance, the remote session agent 1116 may accessthe network application 1108 at various intervals, in response to a userrefresh or access command, etc., for updating, refreshing, downloading,or otherwise retrieving the encoded application data. In someembodiments, the server(s) 1102 (e.g., via a VDA) may provide theencoded application data to the remote session agent 1112 in real-time(or at various intervals or refresh rates). In each instance, the remotesession agent 1112 may receive the encoded application data from theserver(s) 1102 via the network connection established by the networkingagent 1110.

The intermediary device 1106 may translate, decipher, decrypt,interpret, or otherwise decode (hereinafter “decode”) the encodedtraffic data from the network applications 1108, e.g., at a networklevel or layer of the intermediary device using or leveraging onhardware (e.g., processor(s)) of the intermediary device. Decode (andvariations thereof, such as decoded, decoding, etc.), as used herein,can refer to producing a data format or structure (e.g., at networklevel or layer according to the OSI model) which is renderable at adevice without further processing. The intermediary device 1106 maydecode the encoded traffic from the network applications 1108 on-boardusing the SoC 1114, for example. The SoC 1114 may be or include anintegrated circuit or hardware device that includes one or morecomponents of a computer or other electronic system. For instance, theSOC 1114 may include a central processing unit (CPU), memory, I/O portsfor receiving data, secondary storage, etc. The SoC 1114 may includeother components depending on various applications. In some embodiments,the SoC 1114 corresponds to one or more processors or circuitrydedicated to processing or decoding remote-hosted provisioning traffic(e.g., for network application sessions), at network level or layer forexample. In this regard, the SoC 1114 may be specifically designed orimplemented to handle remote provisioning and network traffic-typeprocessing and/or decoding.

In some embodiments, the remote session agent 1112 may route theapplication data to the SoC 1114 for decoding, e.g., at the networklayer or another layer of the OSI model. This can offload the decodingand/or processing of the application data from the client device tohardware on the intermediary device. The intermediary device (e.g., SoC1114) can operate, function and/or act as a client application (e.g.,Citrix Receiver HDX engine) that processes or optimises traffic atnetwork level. In some embodiments, the remote session agent 1112 mayroute all application data to the SoC 1114 for decoding or processing,irrespective of whether the application data is in an encoded format. Incertain embodiments, the remote session agent 1112 may identify a subsetof application data for routing to the SoC 1112 for decoding. The subsetmay include application data which is encoded (or encoded in a certainformat, such as AVC/H.264 encoding). The remote session agent 1112 mayidentify the subset based on which network application 1108 is providingthe application data, the specific structure, format, or container forthe application data, etc.

The SoC 1114 may be designed or implemented to decode the traffic fromthe network applications 1108, e.g., at the network layer or level. Forinstance, the SoC 1114 may include a decoder. The decoder may bedesigned or implemented to decode encoded traffic from the networkapplications 1108 into a renderable format. The encoded traffic caninclude network layer packets. The decoder can decode encoded payloadand/or header information in the network layer packets. In someembodiments, the SoC 1114 may include a plurality of decoders. Eachdecoder may be network application-specific. For instance, theintermediary device 1106 may select, retrieve and/or activate one ormore decoders from a decoder store. The decoders may be selected whenapplications are installed, stored, executed, accessed, etc. at theserver(s) 1102, and/or accessed or delivered via the intermediarydevice. In some embodiments, the decoders may be stored locally on theSoC 1114 (e.g., in memory or secondary storage). In some embodiments,the decoders may be packaged with the network applications 1108 andretrieved by the intermediary device 1106 when the network applications1108 are installed or otherwise stored on the server(s) 1102. Thedecoders may also be provided by the server(s) 1102 to the intermediarydevice 1106 when the network application 1108 is installed, stored,accessed, etc. In some embodiments, the decoders may be hardwaredecoders, such as the AVC/H/264 hardware decoder. The decoders may bebuilt into the SoC 1114. Hence, the decoders may be hardware or softwarewhich is used by the SoC 1114 to decode the encoded application data.

The SoC 1114 may decode the application data at the intermediary device1106 for rendering. The SoC 1114 may decode the application data forrendering at the client device 1104 (e.g., within an embedded browser ofthe client application 1116). The SoC 1114 may decode the applicationdata for rendering at the intermediary device 1106 (e.g., within asecure browser of the intermediary device 1106, as discussed below). TheSoC 1114 may decode the encoded application data according to theencoding protocol. For instance, the various decoders of the SoC 1114may be or include various encoding protocols for encoding and decodingvarious types of data. The SoC 1114 may decode the encoded applicationdata according to the encoding protocols for the specific types ofapplication data. The application data can include graphics data, audiodata and/or other types of data. Some types of data can be communicatedto the intermediary device via one or more virtual channels. The SoC1114 may decode, process and/or optimize any of these data at theintermediary device, thereby offloading such processing from the clientdevice for instance.

As one example, the SoC 1114 may decode encoded graphics data intodecoded graphics data. For example, the remote session agent 1112 of theintermediary device 11106 may receive encoded graphics data in a JPEGformat or container. The remote session agent 1112 may provide theencoded graphics data to the SoC 1114. The SoC 1114 may decode theencoded graphics data into decoded graphics data, such as in bitmapformat, which is renderable at the client device 1104 without furtherprocessing (e.g., without further decoding).

As another example, the SoC 1114 may decode encoded audio data intodecoded audio data. For example, the remote session agent 1112 of theintermediary device 1106 may receive encoded audio data in an MP3 formator container. The remote session agent 1112 may provide the encodedaudio data to the SoC 1114. The SoC 1114 may decode the encoded audiodata into raw audio format which is renderable at the client device 1104without further processing.

As still another example, the SoC 1114 may decode encoded UI applicationdata for displaying a UI for the network application 1108. The decodedapplication data may include CSS files. Each CSS file may include aseries of rules which describe, for instance, topography details of thepage such as font, color, text size, etc., various audio or videoformats, etc. The SoC 1114 may decode the encoded application data intoCSS files which are renderable at the client device 1104 without furtherprocessing.

In each of these examples, the remote session agent 1112 receivesencoded application data, which is provided to the SoC 1114. The SoC1114 decodes the encoded application data prior to any of the encodedapplication data being rendered or otherwise provided to the clientdevice 1104. The client device 1104 therefore does not performprocessing or other decoding of the application data from the networkapplications 1108, which is instead performed at the intermediarydevice.

The intermediary device 1106 may be designed or implemented to transmitthe decoded application data to the client application 1116 of theclient device 1104 for rendering or otherwise displaying the userinterface for the network application 1108 to the user. In someembodiments, the networking application 1110 may establish a connectionwith the client device 1104 (in a manner similar to the networkconnection between the intermediary device 1106 and server(s) 1102described above) and the remote session agent 1112 may communicate thedecoded application data to the client application 1116 for rendering.In other embodiments, the intermediary device 1106 may includerespective networking agents 1110 and remote session agents 1112 for thenetwork connection between the server(s) 1102 and intermediary device1106, and for the network connection between the intermediary device1106 and the client device 1104.

The intermediary device 1106 may transmit the decoded application datato the client device 1104 following the intermediary device 1106decoding the application data received by the intermediary device 1106.The remote session agent 1112 may receive decoded application data fromthe SoC 1114 when the application data is decoded (e.g., upon detectingor registering a “stop,” “complete,” or other command from the SoC1114), and can communicate the decoded application data to the clientdevice 1104. In some embodiments, the intermediary device 1106 maytransmit decoded application data (e.g., continuously, or at intervals)to the client device as the intermediary device 1106 decodes the encodedapplication data. The remote session agent 1112 may receive decodedapplication data from the SoC 1114 as it is decoded, and can communicatethe decoded application data to the client device 1104 once the decodedapplication data is received.

In some embodiments, the intermediary device 1106 may determine whetherthe application data is directed to (or otherwise for) a network device(such as a network printer, fax machine, etc.). For instance, the system1100 may include one or more network devices, such as network printers,fax machines, etc. A network connection may be established between theintermediary device 1106 and the network devices by the networking agent1110 in a manner similar to the network connections described above. Theremote session agent 1112 may identify application data for a networkdevice based on, for instance, various data structure characteristics,an address associated with the application data, etc. Where the remotesession agent 1112 identifies the application data is for the networkdevice, the remote session agent 1112 may direct, transmit, or otherwisecommunicate the application data from the intermediary device 1106 tothe network device. For example, the intermediary device 1106, havingprocessed or decoded traffic of network application data locally at theintermediary device 1106, can convey the decoded data directly to anetwork printer for printing (e.g., without further decoding orprocessing at the network printer). Such embodiments provide for directcommunication between the intermediary device 1106 and various networkdevices, which may not be easily accomplished in other designs orimplementations.

In some embodiments, the intermediary device 1106 may be designed orimplemented to provide a secure browser for rendering the decodedapplication data (e.g., at the intermediary device 1106). The securebrowser may be similar to the secure browser 420 described above inreference to at least FIGS. 4, 5, 7, 8, and 10. Network applications (orweb pages accessed by the secure browser) that are configured to beaccessed or rendered in the secure browser can effectively be subject tothe security mechanisms implemented by the secure browser. These networkapplications can be considered to be contained (e.g., securely) withinthe secure container. The use of such a secure browser can enable anenterprise to implement a content filtering policy in which, forexample, employees are blocked from accessing certain web sites directlyfrom their client devices. The secure browser can be used, for example,to enable client device users to access a corporate intranet without theneed for a VPN.

The secure browser may render the decoded application data on behalf ofthe client device. The secure browser may for instance generate andrender a user interface for the network application 1108 at theintermediary device 1106. When the application data (e.g., userinterface) is rendered at the intermediary device 1106 (e.g., on thesecure browser), the intermediary device 1106 may communicate raw ordecoded data (e.g., corresponding to the rendered application data) tothe client device 1104. The rendered application data (e.g., in bitmapform) may be used by the client device 1104 to render, display orotherwise provide the user interface at the client device 1104. Forinstance, the intermediary device 1106 may provide bitmap data to theclient device 1104 which is communicated to the display for the clientdevice 1104, effectively mirroring the secure browser on the clientdevice 1104. Similarly, the intermediary device 1106 may provide RAWaudio data to the client device which is communicated to speakers forthe client device 1104. In each of these embodiments, the client device1104 can operate as a dummy rendering or display device. Suchembodiments may maintain the integrity of the client device 1104 andallows a user to access unsecure or unsanctioned pages or networkapplications through a secure browser hosted at the intermediary device.

In some embodiments, the intermediary device 1106 can cause an embeddedbrowser integrated in the client application 1116 to render the decodedapplication data. The embedded browser may be similar to the embeddedbrowser 410 described above in reference to at least FIGS. 4 and 8. Theembedded browser can include elements and functionalities of a webbrowser application or engine. The embedded browser can locally rendernetwork application(s) as a component or extension of the clientapplication 1116. The embedded browser can be embedded or incorporatedinto the client application 1116 via any means, such as directintegration (e.g., programming language or script insertion) into theexecutable code of the client application 1116, or via plugininstallation. For example, the embedded browser can include a Chromiumbased browser engine or other type of browser engine, that can beembedded into the client application 1116, using the Chromium embeddedframework (CEF) for instance. The embedded browser can include aHTML5-based layout graphical user interface (GUI). The embedded browsercan provide HTML rendering and JavaScript support to a clientapplication incorporating various programming languages. For example,elements of the embedded browser can bind to a client application 1116incorporating C, C++, Delphi, Go, Java, .NET/Mono, Visual Basic 6.0,and/or Python.

In embodiments where the decoded application data includes CSS files,the embedded browser (or secure browser) may parse the CSS files toconstruct a rendering of the user interface for the network application1108. The embedded browser (or secure browser) may render the userinterface according to the CSS files (e.g., with various widgets locatedand constructed according to the specifications of the CSS files). Theembedded browser may display the user interface to the user for access.Accordingly, the user may interact with the user interface of thenetwork application 1108 on the client device 1104, which has beendecoded at the intermediary device 1106 (e.g., on the SoC 1114). In someembodiments, the user interface may be rendered and displayed at theclient device 1104 as the data from the network application 1108 isreceived and decoded at the SoC 1114. In this regard, traffic from thenetwork application 1108 is decoded and communicated to the embeddedbrowser (or secure browser) on a gradual, dynamic or continuous basis.Such embodiments may improve user experience in accessing the networkapplication.

In some embodiments, the intermediary device 1106 may optimize thereceived application data for rendering at or otherwise providing toclient device 1104. Optimize, as used herein, can refer to modificationof data to achieve performance characteristics in accordance with clientdevice specific characteristics. For instance, the SoC 1114 mayreconfigure or modify the application data prior to the data beingrendered at the client device. The SoC 1114 may reconfigure or modifythe application data to improve the efficiency of retrieval, rendering,or providing of the application data (or raw data) to the client device1104. The SoC 1114 may optimize the application data according tovarious specifications of the client device 1104, such as displayresolution or scale, coloring options, frame refresh rate, speakeroutput capabilities, etc. Such client device 1104 specifications may becommunicated (e.g., by the client device 1104) to the intermediarydevice 1106 when the networking agent 1110 establishes networkconnection between the intermediary device 1106 and client device 1104,for instance.

The SoC 1114 may select various configurations of the application dataaccording to the specifications of the client device 1104. The SoC 1114may select configurations of the application data to achieve variousperformance characteristics of the client device 1104, such as devicespeed, clarity of the display or user interface rendered thereon, audiosound, etc. As one example, the SoC 1114 may select a lower resolutionfor increased battery life of a client device 1104 where the clientdevice 1104 is a mobile device. As another example, the SoC 1114 mayselect a higher display scale for a client device 1104 having arelatively large display. As still another example, the SoC 1114 mayselect different coloring options depending on display type for theclient device 1104 (e.g., high definition versus standard definition,LED). In each of these examples, the SoC 1114 can modify the applicationdata to achieve performance characteristics in accordance with specificcharacteristics of the client device 1104. Hence, the intermediarydevice 1106 can optimize the application data.

In some embodiments, the intermediary device 1106 may monitor thetraffic communicated between the network application 1108, theintermediary device 1106 and/or the client device 1104. For instance,the intermediary device 1106 can monitor the received traffic (e.g., inencrypted packet form), and also have full visibility into thedecrypted/decoded data stream and/or the SSL stack. This visibility canallow the intermediary device 1106 to perform or facilitate policy-basedmanagement (e.g., including data loss prevention (DLP) capabilities),application control (e.g., to improve performance, service level), andcollection and production of analytics. For instance, such visibilitycan provide an information technology (IT) administrator with acontrolled system for deploying web and SaaS applications through theCEB, and allow the IT administrator to set policies or configurationsvia the CEB for performing any of the forgoing activities.

In some embodiments, the intermediary device 1106 may maintain a stateof the network application 1108 when the client device 1104 disconnectsfrom a session of the network application 1108. The intermediary device1106 may maintain a state of the network application 1108 when a sessionof the network application 1108 is transferred from a client device 1104to another client device 1104. During the session of the networkapplication 1108, the intermediary device 1106 may maintain a state ofoperation for the network application 1108. The state of operation forthe network application 1108 may include an executioncode/line/sub-routine identifier/indicator, a cache state, aninput/output (I/O) state, a UI state, and combinations thereof. Theintermediary device 1106 may cache some (or all) of these states ofoperation. In some embodiments, the intermediary device 1106 may send amessage (e.g., by the remote session agent 1112 over the communicationlink established by the networking agent 1110) to the server 1102 topause execution or store/cache some or all of these states of operationfor the network application 1108, e.g., in response to the client devicedisconnecting from a session of the network application. The states ofoperation may be stored or cached, for instance, until the user of theclient device 1104 resumes to the session on the same client device (oron a different client device 1104. In some embodiments, the states ofoperation (also referred to as session state) may be stored or cacheduntil an expiration time. Such embodiments may increase user experienceby improving mobility of application sessions and preventing unintendedsession data loss.

Referring to FIG. 12, depicted is a flow diagram of one embodiment of amethod for delivering a network application. The functionalities of themethod may be implemented using, or performed by, the componentsdetailed herein in connection with FIGS. 1-11. In brief overview, anintermediary device establishes a connection with a network application(1205). The intermediary device receives encoded application data(1210). The intermediary device decodes the application data (1215). Theintermediary device transmits application data to a client application(1220).

Referring now to operation (1205), and in some embodiments, anintermediary device establishes a connection with a network application.In some embodiments, the intermediary device is located between a clientdevice and a server hosting the network application. The intermediarydevice may be located closer to the client device than the server. Forinstance, the intermediary device may locate geographically closer tothe client device. In some embodiments, the intermediary device maylocate closer to the client device in terms of network path length. Theintermediary device may be better suited or positioned to perform theprocessing and optimizing of network traffic from the server. Theintermediary device may provide a better user experience by performingthe processing on-board, which may increase the consistency of graphicsdecoding across client device platforms.

In some embodiments, the intermediary device may include a networkingagent. The networking agent can establish or facilitate establishment ofa network connection between the intermediary device and the server(which hosts the network applications). The networking agent can performhandshaking for a requested connection from the client application orclient device to access a network application, and can establish therequested connection. The networking agent can for example perform thehandshaking for the requested connection following a user selecting anicon or other link associated with launching or otherwise opening thenetwork application (e.g., displayed on the client application of theclient device). In some embodiments, the networking agent can performthe handshaking for the requested connection responsive to the networkapplication being installed or otherwise included on the server.

In some embodiments, the networking agent may establish a secure orencrypted connection. For instance, the networking agent may connect tothe server via a VPN connection, for instance. For example, thenetworking agent can establish a SSL VPN connection between theintermediary device and the server.

In some embodiments, the networking agent may be designed or implementedto form, maintain or establish an HTTP session with the server. Thenetworking agent may establish a TCP connection to the server forinstance. The networking agent can exchange various commands with theserver within the HTTP session in accordance with TCP. In someembodiments, the networking agent may establish a secure HTTP session ina manner similar to the secure or encrypted connections described above.Thus, the networking agent can generally establish or facilitateestablishment of the network connection between the server and theintermediary device, which may be a secure network connection (e.g., SSLVPN) in some embodiments.

The intermediary device may be designed or implemented to initiate aprovisioning session for a remotely-hosted application or desktopsession. The intermediary device may initiate the provisioning sessionwithin or across the network connection established by the networkingagent. In some embodiments, the intermediary device may include a remotesession agent. The remote session agent may initiate the provisioningsession (e.g., which is established using Citrix HDX, ICA protocol, orRDP). The remote session agent may initiate the provisioning session inaccordance with any type or form of protocols, such as RDP, ALP, RFBProtocol, and ICA Protocol. The remote session agent can initiate theprovisioning session for a user of the client device to access thenetwork application.

In some embodiments, at least one of the network applications may be aremote-hosted desktop, a remote-hosted application, or asoftware-as-a-service (SaaS) application. The remote-hosted desktop maybe a virtual desktop hosted on the server which is accessed by theclient device. Hence, the user can remotely operate the virtual desktop,which is hosted at the server, from the client device. In someembodiments, the remote-hosted desktop may be HDX-based, ICA-based,RDP-based, etc., as described above. A remote-hosted application may bean application which is installed within a remote-hosted desktopenvironment and is therefore accessible within the remote-hosteddesktop. A SaaS application is a centrally-hosted application which istypically accessible on a subscription basis. In some embodiments, theSaaS applications may include web-based applications. In otherembodiments, the SaaS applications may include remote-hosted applicationand, therefore, are HDX/ICA/RDP-based applications.

Referring now to operation (1210), and in some embodiments, theintermediary device receives encoded application data. In someembodiments, the intermediary device may receive the encoded applicationvia the network connection established at operation (1205). Theintermediary device may receive encoded application data from thenetwork application. The encoded application data may include encodedgraphics data or encoded audio data.

The network application may execute commands, processes, instructions,etc. at the server. For instance, the network application and/or a VDAmay generate application data using various protocols described above(e.g., RDP, ALP, RFB, ICA protocol). Such protocols can allow UIelements of an application or desktop session or other application datanatively hosted on the server to be provisioned across a network toanother device for example. Those UI elements and other application datacan be encoded (e.g. by the VDA) using such protocols, and delivered orotherwise provisioned to the intermediary device. Thus, the applicationdata may be usable to generate a UI for the network application. Theapplication data may include data which corresponds to UI commands. TheUI commands may include commands for forming widgets of the UI (e.g.,size, location, type, visual characteristics). In some embodiments, theapplication data may include control or configuration traffic forregulating various traffic characteristics of communications from theserver, such as data rate, service level agreements, etc. In someembodiments, the application data can include application state, varioususer profile information, user-generated data, cache data, etc. In someembodiments, the application data may include graphics or audio data.

The network applications and/or a VDA may generate the application datain an encoded format. In other embodiments, the network applications maygenerate the application data in a decoded format, and encode theapplication data prior to transmitting the application to data to theintermediary device. In some embodiments, the network application mayencode the application data in a format which is accessible or decodableby network application-specific software. For instance, the applicationdata may be in an encoded format which is decoded to generate cascadingstyle sheet (CSS) files prior to rendering to form a user interface forthe network application.

The intermediary device may receive the encoded application data fromthe network application on the server via the network connectionestablished by the networking agent. The remote session agent of theintermediary device may receive the encoded application data (or theremote provisioning session may provide the encoded application data tothe remote session agent). Hence, the remote session agent may receivethe encoded application data.

Referring now to operation (1215), and in some embodiments, theintermediary device decodes the application data. In some embodiments,the intermediary device decodes the received application data of thenetwork application into at least one of decoded graphics data ordecoded audio data for rendering at the client device. Although graphicsand/or audio data are sometimes referenced in this disclosure, these aremerely by way of example and not intended to be limiting in any way. Anytype or form of application data (e.g., from any virtual channel of aprovisioning session) can similarly apply, e.g., multimedia data, diskdata, clipboard data, printer data, and so on.

The intermediary device may decode the encoded application data from thenetwork application. The intermediary device may decode the encodedapplication data from the network application on-board by the SoC. TheSoC may be or include an integrated circuit, processor or hardwaredevice that includes one or more components of a computer or otherelectronic system. For instance, the SoC may include a centralprocessing unit (CPU), memory, I/O ports for receiving data, and/orsecondary storage, etc.

The SoC may be designed or implemented to decode the traffic (e.g.,application data) from the network application. For instance, the SoCmay include a decoder. The decoder may be designed or implemented todecode encoded traffic from the network applications into a renderableformat. In some embodiments, the SoC may include a plurality ofdecoders. Each decoder may be network application-specific. Forinstance, the intermediary device (e.g., the remote session agent) mayretrieve decoders from a decoder store. The remote session agent mayretrieve decoders when applications are installed, stored, accessed,etc. at the server. The decoders may be stored locally on the SoC (e.g.,in memory or secondary storage). In some embodiments, the decoders maybe packaged with the network applications. In these embodiments, thedecoders may be retrieved by the remote session agent when the networkapplications are installed or otherwise stored on the server. In someembodiments, the server may provide the decoder to the remote sessionagent when the network applications are installed, stored, accessed,etc. In some embodiments, the decoders may be hardware decoders, such asor similar to the AVC/H/264 hardware decoder. The decoders may be builtinto the SoC 1114. Hence, the decoders may be hardware or software whichis used by the SoC 1114 to decode the encoded application data.

The SoC may decode the application data at the intermediary device forrendering. In some embodiments, the SoC may decode the application dataat the intermediary device for rendering at the client device (e.g.,within the client application). In other embodiments, the SoC may decodethe application data at the intermediary device for rendering at theintermediary device (e.g., by a secure browser, as discussed below). TheSoC may decode the encoded application data according to an encodingprotocol. For instance, the various decoders of the SoC may be orinclude various encoding protocols for encoding and decoding varioustypes of data from corresponding applications. The SoC may decode theencoded application data according to the encoding protocols for thespecific types of application data.

In some embodiments, the intermediary device may optimize the receivedapplication data (e.g., at a network layer or level) for rendering at orotherwise providing to client device. The intermediary device canoffload processing, optimization and/or decoding of the application datafrom the client device, to hardware of the intermediary device. Forinstance, the SoC may reconfigure or modify the application data priorto the data being rendered at the client device. The SoC may reconfigureor modify the application data to improve the efficiency of retrieval,rendering, or providing of the application data (or raw data) to theclient device. The SoC may optimize the application data according tovarious specifications of the client device, such as display resolutionor scale, coloring options, frame refresh rate, speaker outputcapabilities, etc. Such client device specifications may be communicated(e.g., by the client device) to the intermediary device when thenetworking agent establishes network connection between the intermediarydevice and client device. The SoC may select various configurations ofthe application data according to the specifications of the clientdevice. The SoC may select configurations of the application data toachieve various performance characteristics of the client device, suchas device speed, clarity of the display or user interface renderedthereon, audio sound, etc. Thus, the SoC can modify the application datato achieve performance characteristics in accordance with specificcharacteristics of the client device, hence optimizing the applicationdata.

In some embodiments, the intermediary device may provide a securebrowser for rendering the decoded application data (e.g., rendering thedecoded application data at the intermediary device). Networkapplications (or web pages accessed by the secure browser) that areconfigured to run within the secure browser can effectively be subjectto the security mechanisms implemented by the secure browser. The use ofsuch a secure browser can enable an enterprise to implement a contentfiltering policy in which, for example, employees are blocked fromaccessing certain web sites or other unsanctioned content or sourcesfrom their client devices.

The secure browser may render the decoded application data on behalf ofthe client device. The secure browser may for instance render the userinterface for the network application at the intermediary device. Whenthe application data (e.g., user interface) is rendered at theintermediary device (e.g., on the secure browser), the intermediarydevice may communicate raw or decoded data (e.g., corresponding to therendered application data) to the client device. The renderedapplication data (e.g., in bitmap form) may be used by the client deviceto render, display, or otherwise provide the user interface at theclient device. For instance, the intermediary device may provide bitmapdata to the client device which is communicated to the display for theclient device, effectively mirroring the secure browser on the clientdevice. Similarly, the intermediary device may provide RAW audio data tothe client device which is communicated to speakers for the clientdevice. In each of these embodiments, the client device acts as a dummyrendering or display device. Such embodiments may maintain the integrityof the client device and allows a user to access unsecure orunsanctioned pages or applications through a secure browser hosted atthe intermediary device.

Referring now to operation (1220), and in some embodiments, theintermediary device transmits the application data to a clientapplication data. In some embodiments, the intermediary device transmitsthe decoded graphics data and/or decoded audio data to a clientapplication of the client device for rendering to provide user access tothe network application. In some embodiments, the networking applicationmay establish a connection with the client device (in a manner similarto the network connection established between the intermediary deviceand server(s) described above) and the remote session agent maycommunicate the decoded application data to the client application forrendering. In other embodiments, the intermediary device may includerespective networking agents and remote session agents for the networkconnection between the server and intermediary device, and for thenetwork connection between the intermediary device and client device.

The intermediary device may transmit the decoded application data to theclient device following the decoding of the application data received bythe intermediary device. The remote session agent may receive decodedapplication data from the SoC when the application data is decoded, andcan communicate the decoded application data to the client device. Insome embodiments, the intermediary device may transmit the decodedapplication data as the intermediary device decodes the encodedapplication data. The remote session agent may receive decodedapplication data from the SoC as it is decoded, and communicate thedecoded application data to the client device once the decodedapplication data is received. In this regard, the client device mayrender the decoded application data all at once, or as portions of thedecode data is received.

In some embodiments, the intermediary device may cause an embeddedbrowser integrated in the client application to render the decodedapplication data. The embedded browser can locally render networkapplication(s) as a component or extension of the client application.

In embodiments where the decoded application data is CSS files, theembedded browser (or secure browser) may parse the CSS files toconstruct a rendering of the user interface for the network application.The embedded browser (or secure browser) may render the user interfaceaccording to the CSS files (e.g., with various widgets located andconstructed according to the specifications of the CSS files). Theembedded browser (or secure browser) may display the user interface tothe user for access. Accordingly, the user may interact with the userinterface of the network application rendered on the client device. Insome embodiments, the user interface may be rendered and displayed atthe client device using the data decoded at the SOC. In this regard,traffic from the network application is decoded and communicated to theembedded browser for rendering or display.

In some embodiments, the intermediary device may monitor the trafficcommunicated between the network application, the intermediary deviceand/or the client device. For instance, the intermediary device canmonitor the received traffic (e.g., in encrypted packet form), and alsohave full visibility into the decrypted data stream and/or the SSLstack. This visibility can allow the intermediary device to perform orfacilitate policy-based management (e.g., including data loss prevention(DLP) capabilities), application control (e.g., to improve performance,service level), and collection and production of analytics.

In some embodiments, the intermediary device may maintain a state of thenetwork application when the client device disconnects from a session ofthe network application. The intermediary device may maintain a state ofthe network application when a session of the network application istransferred from a client device to another client device. During thesession of the network application, the intermediary device may maintaina state of operation for the network application. The state of operationfor the network application may be include an executioncode/line/sub-routine identifier/indicator, a cache state, aninput/output (I/O) state, a UI state, and combinations thereof. Theintermediary device may cache some (or all) of these states ofoperation. In some embodiments, the intermediary device may send amessage (e.g., by the remote session agent over the communication linkestablished by the networking agent) to the server to pause execution orstore/cache some or all of these states of operation for the networkapplication, e.g., in response to the client device disconnecting from asession of the network application. The states of operation may bestored or cached, for instance, until the user of the client deviceresumes the session on the same client device (or on a different clientdevice). In some instances, the states of operation (also referred to assession state) may be stored or cached until an expiration time. Suchembodiments may increase user experience by improving mobility ofapplication sessions and preventing unintended data loss.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The systems and methodsdescribed above may be implemented as a method, apparatus or article ofmanufacture using programming and/or engineering techniques to producesoftware, firmware, hardware, or any combination thereof. In addition,the systems and methods described above may be provided as one or morecomputer-readable programs embodied on or in one or more articles ofmanufacture. The term “article of manufacture” as used herein isintended to encompass code or logic accessible from and embedded in oneor more computer-readable devices, firmware, programmable logic, memorydevices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,USB Flash memory, hard disk drive, etc.). The article of manufacture maybe accessible from a file server providing access to thecomputer-readable programs via a network transmission line, wirelesstransmission media, signals propagating through space, radio waves,infrared signals, etc. The article of manufacture may be a flash memorycard or a magnetic tape. The article of manufacture includes hardwarelogic as well as software or programmable code embedded in a computerreadable medium that is executed by a processor. In general, thecomputer-readable programs may be implemented in any programminglanguage, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte codelanguage such as JAVA. The software programs may be stored on or in oneor more articles of manufacture as object code.

While various embodiments of the methods and systems have beendescribed, these embodiments are illustrative and in no way limit thescope of the described methods or systems. Those having skill in therelevant art can effect changes to form and details of the describedmethods and systems without departing from the broadest scope of thedescribed methods and systems. Thus, the scope of the methods andsystems described herein should not be limited by any of theillustrative embodiments and should be defined in accordance with theaccompanying claims and their equivalents.

We claim:
 1. A method comprising: receiving, by a device incommunication via one or more networks with a client device, encodeddata communicated to the client device from an application hosted on theremote computing device, the encoded data to be decoded for rendering ona display of the client device; decoding, by the device, the encodeddata into decoded data, the decoded data being configurable based atleast on one or more characteristics of the client device; andtransmitting, by the device via the one or more networks, the decodeddata, instead of the encoded data, to the client device to render to thedisplay, the decoded data to provide access to the application via theclient device.
 2. The method of claim 1, wherein the communicationsbetween the remote computing device and the client device traverse thedevice.
 3. The method of claim 1, further comprising configuring, by thedevice, the decoded data based at least on a characteristic of theclient device identified by the device.
 4. The method of claim 1,wherein the device decodes the encoded data into decoded data such thatthe decoded data is renderable at the display of the client devicewithout further processing or decoding.
 5. The method of claim 1,wherein the encoded data comprises graphics.
 6. The method of claim 1,wherein the decoded data provides a user interface to display by theclient device.
 7. The method of claim 1, further comprisingtransmitting, by the device, the decoded data to a browser embedded in aclient application of the client device to render the decoded graphics.8. A system comprising: a device in communication via one or morenetworks with a client device and a remote computing device, the deviceconfigured to: receive encoded data communicated to the client devicefrom an application hosted on the remote computing device, the encodeddata to be decoded for rendering by the client device on a display;decode the encoded data into decoded data, the decoded data beingconfigurable based at least on one or more characteristics of the clientdevice; and transmit, via the one or more networks, the decoded data,instead of the encoded data, to the client device to render to thedisplay, the decoded data to provide access to the application via theclient device.
 9. The system of claim 8, wherein the communicationsbetween the remote computing device and the client device traverse thedevice.
 10. The system of claim 8, wherein the device is furtherconfigured to configure the decoded data based at least on acharacteristic of the client device identified by the device.
 11. Thesystem of claim 8, wherein the device is further configured to decodethe encoded data into decoded data such that the decoded data isrenderable at the display of the client device without furtherprocessing or decoding.
 12. The system of claim 8, wherein the encodeddata comprises graphics.
 13. The system of claim 8, wherein the decodeddata provides a user interface to display by the client device foraccessing the application.
 14. The system of claim 8, wherein the deviceis further configured to transmit to the decoded data to a browserembedded in a client application of the client device to render thedecoded data.
 15. A non-transitory computer-readable medium storinginstructions that, when executed by one or more processors of a devicein communication via one or more networks with a client device and aremote computing device, cause the one or more processors to: receiveencoded data communicated to the client device from an applicationhosted on the remote computing device, the encoded data to be decodedfor rendering by the client device on a display; decode the encoded datainto decoded data, the decoded data being configurable based at least onone or more characteristics of the client device; and transmit, via theone or more networks, the decoded data, instead of the encoded data, tothe client device to render to the display, the decoded data to provideaccess to the application via the client device.
 16. The non-transitorycomputer-readable medium of claim 15, further comprising instructionsconfigured to cause the one or more processors to configure the decodeddata based at least on a characteristic of the client device identifiedby the device.
 17. The non-transitory computer-readable medium of claim15, further comprising instructions configured to cause the one or moreprocessors to decode the encoded data into decoded data such that thedecoded data is renderable at the display of the client device withoutfurther processing or decoding.
 18. The non-transitory computer-readablemedium of claim 15, wherein the encoded data comprises graphics.
 19. Thenon-transitory computer-readable medium of claim 15, wherein the decodeddata provides a user interface to display by the client device foraccessing the application.
 20. The non-transitory computer-readablemedium of claim 15, further comprising instructions configured to causethe one or more processors to transmit to the decoded data to a browserembedded in a client application of the client device to render thedecoded data.